Merge pull request #314854 from mukesh-dua/release-microsoft-discovery

Update links and add new Bookshelf & Knowledge Bases article; enhance documentation with images and toc updates which were removed with previous PR merge

Author: Carolyn135

articles/microsoft-discovery/concept-azure-container-registry.md

@@ -221,5 +221,5 @@ When you develop and publish tools for Microsoft Discovery, the containerized to
 - [What is Microsoft Discovery?](overview-what-is-microsoft-discovery.md)
 - [Virtual networks and subnets in Microsoft Discovery](concept-virtual-networks.md)
 - [Role assignments in Microsoft Discovery](concept-role-assignments.md)
-- [Azure Container Registry documentation](https://learn.microsoft.com/azure/container-registry/)
+- [Azure Container Registry documentation](/azure/container-registry/)
 - [Azure Private Endpoint overview](../private-link/private-endpoint-overview.md)

…/concept-bookshelf-and-knowledgebases.md …ery/concept-bookshelf-knowledge-bases.mdarticles/microsoft-discovery/concept-bookshelf-and-knowledgebases.md renamed to articles/microsoft-discovery/concept-bookshelf-knowledge-bases.md articles/microsoft-discovery/concept-bookshelf-and-knowledgebases.md renamed to articles/microsoft-discovery/concept-bookshelf-knowledge-bases.md

@@ -35,7 +35,7 @@ Currently, the Bookshelf supports indexing unstructured (text-based) file format
 * JSON
 * CSV
 
-The Bookshelf uses Azure AI Search Enrichment to process supported file formats. Images embedded in supported file formats are processed using Azure AI Search's built-in [Vision skill](https://learn.microsoft.com/azure/ai-services/computer-vision/overview), which automatically generates alt-text for embedded images. See [Azure AI Search's documentation](https://microsoftapc.sharepoint.com/:x:/t/ProjectParagon/IQDSrYORrkMDSa9OME93rcyYAc2EV_jDqr9aD3jYTThB7Cs?e=DfOv2t)for the full list of supported file formats.
+The Bookshelf uses Azure AI Search Enrichment to process supported file formats. Images embedded in supported file formats are processed using Azure AI Search's built-in [Vision skill](/azure/ai-services/computer-vision/overview), which automatically generates alt-text for embedded images. See [Azure AI Search's documentation](/azure/search/cognitive-search-skill-document-intelligence-layout#supported-file-formats) for the full list of supported file formats.
 
 The knowledge graph and vector database that results from indexing, collectively known as a Knowledge Base (KB), are stored in an Azure SQL DB in your subscription.
 

articles/microsoft-discovery/concept-discovery-engine.md

@@ -119,7 +119,7 @@ When cognition executes tasks, it draws on the full Microsoft Discovery platform
 
 - **[Agents](concept-discovery-agent.md)**: Specialized AI systems that execute specific types of work. Cognition selects the agent whose capabilities best match each task. An agent is associated to the best model for the type of work required. 
 - **Tools**: Containerized executables that run on the [supercomputer](how-to-manage-supercomputers.md) for computation, data processing, and analysis. Tools handle work that requires specialized software or significant compute resources.
-- **[Bookshelf](concept-bookshelf-and-knowledgebases.md)**: Knowledge bases built from your documents and scientific literature. Agents query bookshelves to ground their reasoning in relevant context.
+- **[Bookshelf](concept-bookshelf-knowledge-bases.md)**: Knowledge bases built from your documents and scientific literature. Agents query bookshelves to ground their reasoning in relevant context.
 
 You configure these resources when you set up your workspace and project. Cognition then orchestrates them automatically based on what each task requires.
 

articles/microsoft-discovery/concept-projects-investigations.md

@@ -102,4 +102,4 @@ Subscription
 - [Add agents using bundles](quickstart-agents-bundles.md)
 - [Microsoft Discovery agents](concept-discovery-agent.md)
 - [Agent types in Microsoft Discovery](concept-discovery-agent-types.md)
-- [Bookshelf & Knowledge Bases](concept-bookshelf-and-knowledgebases.md)
+- [Bookshelf & Knowledge Bases](concept-bookshelf-knowledge-bases.md)

articles/microsoft-discovery/concept-resource-provider-registration.md

@@ -86,7 +86,7 @@ Refresh the **Resource providers** page and confirm that all the Resource Provid
 
 #### Prerequisites
 
-- [Azure CLI installed](https://learn.microsoft.com/cli/azure/install-azure-cli)
+- [Azure CLI installed](/cli/azure/install-azure-cli)
 - Authenticated to your Azure account (`az login`)
 
 #### Register the resource provider
@@ -113,7 +113,7 @@ az provider list --query "[].{Provider:namespace, Status:registrationState}" --o
 
 #### Prerequisites
 
-- [Azure PowerShell module installed](https://learn.microsoft.com/powershell/azure/install-azure-powershell)
+- [Azure PowerShell module installed](/powershell/azure/install-azure-powershell)
 - Authenticated to your Azure account (`Connect-AzAccount`)
 
 #### Register the resource provider

articles/microsoft-discovery/how-to-data-handling-with-tools-agents.md

@@ -269,7 +269,7 @@ After this mount, the tool container can read files from `/app/inputs/run1/`.
 
 > [!IMPORTANT]
 > Provide only absolute paths in `mountPath`. Relative paths aren't supported. If the URI points to a directory, the directory contents are placed at the mount path. If the URI points to a file, the file is placed at the mount path.
-> If not specified explicitly, default value for input is /app/inputs and for and output mounts, it's /app/outputs.
+> If not specified explicitly, default value for input is /app/inputs and for output mounts, it's /app/outputs.
 
 ### Tell the agent which paths to use in tool descriptions
 
@@ -409,5 +409,5 @@ If a resource doesn't appear in your conversation, use the following steps:
 
 - [Microsoft Discovery agents](concept-discovery-agent.md)
 - [Agent types in Microsoft Discovery](concept-discovery-agent-types.md)
-- [Bookshelf and knowledge bases](concept-bookshelf-and-knowledgebases.md)
+- [Bookshelf and knowledge bases](concept-bookshelf-knowledge-bases.md)
 - [Storage assets and storage containers in Microsoft Discovery](concept-storage-account.md)

articles/microsoft-discovery/how-to-deploy-network-hardened-stack.md

@@ -246,4 +246,4 @@ When you complete this deployment, you have:
 ## Next steps
 
 - [Configure network security](how-to-configure-network-security.md) - detailed network hardening and PE setup
-- [Bookshelf and Knowledge Bases](concept-bookshelf-and-knowledgebases.md)
+- [Bookshelf and Knowledge Bases](concept-bookshelf-knowledge-bases.md)

articles/microsoft-discovery/how-to-manage-supercomputers.md

@@ -99,7 +99,7 @@ Nodepools define the compute capacity (VMs) attached to a Supercomputer. You can
 2. Under **Settings**, select **Nodepools**.
 3. Select **Create**.
 
-   :::image type="content" source="./media/how-to-manage-supercomputers/create-supercomputer-nodepool-create.jpg" alt-text="Screenshot of Azure portal showing Supercomputer create nodepool page." lightbox="./media/how-to-manage-supercomputers/create-supercomputer-nodepool-create.jpg":::
+   :::image type="content" source="./media/how-to-manage-supercomputers/create-supercomputer-node-pool-create.jpg" alt-text="Screenshot of Azure portal showing Supercomputer create nodepool page." lightbox="./media/how-to-manage-supercomputers/create-supercomputer-node-pool-create.jpg":::
 
 ### Configure basic settings
 
@@ -123,7 +123,7 @@ Nodepools define the compute capacity (VMs) attached to a Supercomputer. You can
 
 1. Choose a **Virtual Machine type** for the Node Pool.
 
-   :::image type="content" source="./media/how-to-manage-supercomputers/create-supercomputer-nodepool-vm-configuration.jpg" alt-text="SCreenshot of Azure portal showing Nodepool select VM type." lightbox="./media/how-to-manage-supercomputers/create-supercomputer-nodepool-vm-configuration.jpg":::
+   :::image type="content" source="./media/how-to-manage-supercomputers/create-supercomputer-node-pool-vm-configuration.jpg" alt-text="SCreenshot of Azure portal showing Nodepool select VM type." lightbox="./media/how-to-manage-supercomputers/create-supercomputer-node-pool-vm-configuration.jpg":::
 
 > [!NOTE]
 > The selected Virtual Machine type must be available and quota-approved in the selected region.
@@ -134,7 +134,7 @@ Nodepools define the compute capacity (VMs) attached to a Supercomputer. You can
 
 Specify the **maximum node count**, which defines the upper bound for automatically scaling.
 
-   :::image type="content" source="./media/how-to-manage-supercomputers/create-supercomputer-nodepool-scaling.jpg" alt-text="Screenshot of Azure portal showing Nodepool scaling options." lightbox="./media/how-to-manage-supercomputers/create-supercomputer-nodepool-scaling.jpg":::
+   :::image type="content" source="./media/how-to-manage-supercomputers/create-supercomputer-node-pool-scaling.jpg" alt-text="Screenshot of Azure portal showing Nodepool scaling options." lightbox="./media/how-to-manage-supercomputers/create-supercomputer-node-pool-scaling.jpg":::
 
 ### Create the Nodepool
 
@@ -158,7 +158,7 @@ To delete the nodepools, follow these steps:
     - Select the Supercomputer that owns the nodepool.
 3. Select the **Nodepool** under **Settings** in the left pane.
 
-   :::image type="content" source="./media/how-to-manage-supercomputers/delete-nodepool.jpg" alt-text="Screenshot of Azure portal showing nodepools." lightbox="./media/how-to-manage-supercomputers/delete-nodepool.jpg":::
+   :::image type="content" source="./media/how-to-manage-supercomputers/delete-node-pool.jpg" alt-text="Screenshot of Azure portal showing nodepools." lightbox="./media/how-to-manage-supercomputers/delete-node-pool.jpg":::
 
 4. Select the nodepool or nodepools that you want to delete and select **Delete**
 1. Wait for all the nodepools to get deleted, then navigate to the supercomputer and select the **Overview** section in the left pane