Merge pull request #307143 from MicrosoftDocs/main

Auto Publish – main to live - 2025-10-20 22:00 UTC

Author: learn-build-service-prod[bot]

.openpublishing.redirection.json

@@ -7920,8 +7920,8 @@
       "redirect_document_id": false
     },
     {
-      "source_path": "articles/reliability/reliability-event-hubs.md",
-      "redirect_url": "/azure/event-hubs/event-hubs-business-continuity-outages-disasters",
+      "source_path": "articles/event-hubs/event-hubs-business-continuity-outages-disasters.md",
+      "redirect_url": "/azure/reliability/reliability-event-hubs",
       "redirect_document_id": false
     },
     {
@@ -7939,9 +7939,5 @@
       "redirect_url": "/azure/iot-hub-device-update/",
       "redirect_document_id": false
     }
-
-
-
-    
   ]
 }

articles/active-directory-b2c/partner-grit-app-proxy.md

@@ -18,7 +18,7 @@ ms.subservice: b2c
 
 [!INCLUDE [active-directory-b2c-end-of-sale-notice-b](../../includes/active-directory-b2c-end-of-sale-notice-b.md)]
 
-In this sample tutorial, learn how to migrate a legacy application using header-based authentication to Azure Active Directory B2C (Azure AD B2C) with [Grit's app proxy](https://www.gritiam.com/appProxy.html).
+In this sample tutorial, learn how to migrate a legacy application using header-based authentication to Azure Active Directory B2C (Azure AD B2C) with [Grit's app proxy](https://www.gritiam.com/grit_legacy_app_proxy.html).
 
 Benefits of using Grit's app proxy are as follows:
 
@@ -122,7 +122,7 @@ From the list, select the IdP.
 
 ## Additional resources
 
-- [Grit app proxy documentation](https://www.gritiam.com/appProxy.html)
+- [Grit app proxy documentation](https://www.gritiam.com/grit_legacy_app_proxy.html)
 
 - [Configure the Grit IAM B2B2C solution with Azure AD B2C](partner-grit-iam.md)
 

articles/active-directory-b2c/partner-grit-editor.md

@@ -19,7 +19,7 @@ ms.subservice: b2c
 
 [!INCLUDE [active-directory-b2c-end-of-sale-notice-b](../../includes/active-directory-b2c-end-of-sale-notice-b.md)]
 
-[Grit Software Systems Visual Identity Experience Framework (IEF) Editor](https://www.gritiam.com/iefeditor.html), is a tool that saves time during Azure Active Directory B2C (Azure AD B2C) authentication deployment. It supports multiple languages without the need to write code. It also has a no code debugger for user journeys.
+[Grit Software Systems Visual Identity Experience Framework (IEF) Editor](https://www.gritiam.com/visual_authentication.html), is a tool that saves time during Azure Active Directory B2C (Azure AD B2C) authentication deployment. It supports multiple languages without the need to write code. It also has a no code debugger for user journeys.
 
 Use the Visual IEF Editor to:
 

articles/active-directory-b2c/partner-grit-iam.md

@@ -18,7 +18,7 @@ ms.subservice: b2c
 
 [!INCLUDE [active-directory-b2c-end-of-sale-notice-b](../../includes/active-directory-b2c-end-of-sale-notice-b.md)]
 
-In this tutorial, you learn how to integrate Azure Active Directory B2C (Azure AD B2C) authentication with a [Grit IAM B2B2C](https://www.gritiam.com/b2b2c.html) solution. You can use the solution to provide secure, reliable, self-serviceable, and user-friendly identity and access management to your customers. Shared profile data such as first name, last name, home address, and email used in web and mobile applications are stored in a centralized manner with consideration to compliance and regulatory needs.
+In this tutorial, you learn how to integrate Azure Active Directory B2C (Azure AD B2C) authentication with a [Grit IAM B2B2C](https://www.gritiam.com/IAM_solution_for_B2B2C.html) solution. You can use the solution to provide secure, reliable, self-serviceable, and user-friendly identity and access management to your customers. Shared profile data such as first name, last name, home address, and email used in web and mobile applications are stored in a centralized manner with consideration to compliance and regulatory needs.
 
 
 Use Grit's B2BB2C solution for:
@@ -30,7 +30,7 @@ Use Grit's B2BB2C solution for:
 
 To get started, ensure the following prerequisites are met:
 
-- A Grit IAM account. You can go to [Grit IAM B2B2C solution](https://www.gritiam.com/b2b2c.html) to get a demo.
+- A Grit IAM account. You can go to [Grit IAM B2B2C solution](https://www.gritiam.com/IAM_solution_for_B2B2C.html) to get a demo.
 - A Microsoft Entra subscription. If you don't have one, you can create a [free Azure account](https://azure.microsoft.com/pricing/purchase-options/azure-account?cid=msft_learn).
 - An Azure AD B2C tenant linked to the Azure subscription. You can learn more at [Tutorial: Create an Azure Active Directory B2C tenant](tutorial-create-tenant.md). 
 - Configure your application in the Azure portal. 

articles/azure-functions/functions-bindings-mcp-trigger.md

@@ -34,9 +34,9 @@ private const string BlobPath = "snippets/{mcptoolargs.snippetname}.json";
 public string SaveSnippet(
     [McpToolTrigger("save_snippet", "Saves a code snippet into your snippet collection.")]
         ToolInvocationContext context,
-    [McpToolProperty("snippetname", "The name of the snippet.")]
+    [McpToolProperty("snippetname", "The name of the snippet.", isRequired: true)]
         string name,
-    [McpToolProperty("snippet", "The code snippet.")]
+    [McpToolProperty("snippet", "The code snippet.", isRequired: true)]
         string snippet
 )
 {
@@ -73,7 +73,7 @@ builder.Services
 
 builder
     .ConfigureMcpTool("get_snippets")
-    .WithProperty("snippetname", "string", "The name of the snippet.");
+    .WithProperty("snippetname", "string", "The name of the snippet.", required: true);
 
 builder.Build().Run();
 ```
@@ -448,7 +448,7 @@ The `McpToolPropertyAttribute` type supports these properties:
 | **Description** | Description of what the tool property does.  |
 | **IsRequired** | (Optional) If set to `true`, the tool property is required as an argument for tool calls. Defaults to `false`. |
 
-The property type is inferred from the type of the parameter to which you apply the attribute. For example `[McpToolProperty("snippetname", "The name of the snippet.")] string name` defines a tool property named `snippetname` of type `string` in MCP messages.
+The property type is inferred from the type of the parameter to which you apply the attribute. For example `[McpToolProperty("snippetname", "The name of the snippet.", true)] string name` defines a required tool property named `snippetname` of type `string` in MCP messages.
 
 You can see these attributes used in the `SaveSnippet` tool in the [Examples](#example).
 
@@ -492,7 +492,7 @@ builder.ConfigureFunctionsWebApplication();
 
 builder
     .ConfigureMcpTool("get_snippets")
-    .WithProperty("snippetname", "string", "The name of the snippet.");
+    .WithProperty("snippetname", "string", "The name of the snippet.", required: true);
 
 // other configuration
 

articles/azure-vmware/configure-storage-policy.md

@@ -3,7 +3,7 @@ title: Configure a Storage Policy
 description:  Learn how to configure a storage policy for your Azure VMware Solution virtual machines.
 ms.topic: how-to
 ms.service: azure-vmware
-ms.date: 01/08/2025
+ms.date: 10/20/2025
 ms.custom:
   - engagement-fy23
   - build-2025
@@ -120,6 +120,55 @@ Run the `Set-LocationStoragePolicy` cmdlet to modify vSAN-based storage policies
 
 1. Check **Notifications** to see the progress.
 
+## List storage policies for Unassociated objects 
+
+Unassociated objects in vCenter are vSAN storage objects that are not linked to any active VM or namespace, often resulting from VM deletions or API operations, and may accumulate over time, potentially causing cluster health or capacity issues if not managed. 
+
+Run the `Get-UnassociatedVsanObjectsWithPolicy` cmdlet to list the unassociated vSAN-based Objects with specified storage policy.
+
+1. Select **Run command** > **Packages** > **Microsoft.AVS.Management** > **Get-UnassociatedVsanObjectsWithPolicy**. 
+
+> [!NOTE]
+> Use the latest version of the **Microsoft.AVS.Management** package. 
+
+   :::image type="content" source="media/run-command/run-command-unassociated-storage-policy.png" alt-text="Screenshot that shows how to access the unassociated storage policy run command." lightbox="media/run-command/run-command-unassociated-storage-policy.png":::
+
+2. Provide the required values or change the default values according to the following table. Then select **Run**.
+
+| Field | Value |
+   | --- | --- |
+   | **Policy Name** | Storage Policy Name to filter unassociated objects. Please make sure that the policy name is an exact match. For example, *RAID-1 FTT-1* |
+   | **Cluster Name** | Name of the Cluster to scan for the unassociated objects. For example, Cluster-1 |
+   | **Retain up to**  | Retention period of the cmdlet output. The default value is `60`.  |
+   | **Specify name for execution**  | Alphanumeric name. For example, *Get-UnassociatedVsanObjectsWithPolicy-Exec1*.  |
+   | **Timeout**  |  The period after which a cmdlet exits if it's taking too long to finish.  |
+
+   :::image type="content" source="media/run-command/run-command-get-unassociated-storage-policy.png" alt-text="Screenshot that shows how to list unassociated storage policies." lightbox="media/run-command/run-command-get-unassociated-storage-policy.png":::
+
+   3. Check **Notifications** to see the progress.
+
+## Set a storage policy for Unassociated vSAN objects 
+ 
+Run the `Update-StoragePolicyOfUnassociatedVsanObjects` cmdlet to modify current vSAN-based storage policy to a target storage policy on a cluster. For example, if you have unassociated objects with RAID-5 FTT-1  in Cluster-1, you can set the target policy name as RAID-1 FTT-1.
+
+1. Select **Run command** > **Packages** > **Microsoft.AVS.Management** > **Update-StoragePolicyOfUnassociatedVsanObjects**. 
+
+1. Provide the required values or change the default values according to the following table. Then select **Run**.
+
+| Field | Value |
+   | --- | --- |
+   | **CurrentPolicyName** | Name of the storage policy that the unassociated objects currently have. For example, *RAID-5 FTT-1* |
+   | **TargetPolicyName** | Name of the storage policy that you want to set for the unassociated objects. For example, *RAID-1 FTT-1* |
+   | **Cluster Name** | Name of the Cluster where you want the unassociated objects updated. For example, *Cluster-1* |
+   | **Retain up to**  | Retention period of the cmdlet output. The default value is `60`.  |
+   | **Specify name for execution**  | Alphanumeric name. For example, *Update-StoragePolicyOfUnassociatedVsanObjects-Exec1*.  |
+   | **Timeout**  |  The period after which a cmdlet exits if it's taking too long to finish.  |
+
+   :::image type="content" source="media/run-command/run-command-update-unassociated-storage-policy.png" alt-text="Screenshot that shows how to update unassociated storage policies." lightbox="media/run-command/run-command-update-unassociated-storage-policy.png":::
+
+
+   3. Check **Notifications** to see the progress.
+
 ## Specify a storage policy for a cluster
 
 Run the `Set-ClusterDefaultStoragePolicy` cmdlet to specify a default storage policy for a cluster.

articles/azure-vmware/media/run-command/run-command-get-unassociated-storage-policy.png

@@ -48,7 +48,8 @@ This tutorial uses a premium instance of Azure Container Registry to improve col
     CONTAINERAPPS_ENVIRONMENT="my-environment-name"
     GPU_TYPE="Consumption-GPU-NC24-A100"
     CONTAINER_APP_NAME="llama3-nim"
-    CONTAINER_AND_TAG="llama-3.1-8b-instruct:latest"
+    CONTAINER_AND_TAG="meta/llama-3.1-8b-instruct:latest"
+    NGC_SECRET=<Your NVIDIA NGC API Key>
     ```
 
 [!INCLUDE [container-apps-create-resource-group.md](../../includes/container-apps-create-resource-group.md)]
@@ -67,53 +68,37 @@ This tutorial uses a premium instance of Azure Container Registry to improve col
       --sku premium
     ```
 
-## Pull, tag, and push your image
+## Import the NVIDIA NIM image into your Azure Container Registry
 
-Next, pull the image from NVIDIA GPU Cloud and push to Azure Container Registry.
+Next, import the image from NVIDIA GPU Cloud to Azure Container Registry.
 
 > [!NOTE]
 > NVIDIA NICs each have their own hardware requirements. Make sure the GPU type you select supports the [NIM](https://build.nvidia.com/models?filters=nimType%3Anim_type_run_anywhere&q=llama) of your choice. The Llama3 NIM used in this tutorial can run on NVIDIA A100 GPUs.
 
-1. Authenticate to the NVIDIA container registry.
-
-    ```bash
-    docker login nvcr.io
-    ```
-
-    After you run this command, the sign in process prompts you to enter a username. Enter **$oauthtoken** for your user name value.
-
-    Then you're prompted for a password. Enter your NVIDIA NGC API key here. Once authenticated to the NVIDIA registry, you can authenticate to the Azure registry.
-
 1. Authenticate to Azure Container Registry.
 
     ```bash
     az acr login --name $ACR_NAME
     ```
 
-1. Pull the Llama3 NIM image.
-
-    ```azurecli
-    docker pull nvcr.io/nim/meta/$CONTAINER_AND_TAG
-    ```
-
-1. Tag the image.
-
-    ```azurecli
-    docker tag nvcr.io/nim/meta/$CONTAINER_AND_TAG $ACR_NAME.azurecr.io/$CONTAINER_AND_TAG
-    ```
-
 1. Push the image to Azure Container Registry.
 
     ```azurecli
-    docker push $ACR_NAME.azurecr.io/$CONTAINER_AND_TAG
+    az acr import \
+        --name $ACR_NAME \
+        --source nvcr.io/nim/$CONTAINER_AND_TAG \
+        --image $CONTAINER_AND_TAG \
+        --username '$oauthtoken' \
+        --password $NGC_SECRET
+        
     ```
 
 ## Enable artifact streaming (recommended but optional)
 
-When your container app runs, it pulls the container from your container registry. When you have larger images like in the case of AI workloads, this image pull may take some time. By enabling artifact streaming, you reduce the time needed, and your container app can take a long time to start if you don't enable artifact streaming. Use the following steps to enable artifact streaming.
+When your container app runs, it pulls the container from your container registry. When you have larger images like in the case of AI workloads, this image pull may take some time. By enabling artifact streaming, your container app will load the essential parts of your image first, reducing the amount of time to startup your container. Use the following steps to enable artifact streaming.
 
 > [!NOTE]
-> The following commands can take a few minutes to complete.
+> The following commands can take a long time to complete.
 
 1. Enable artifact streaming on your container registry.
 
@@ -136,7 +121,7 @@ When your container app runs, it pulls the container from your container registr
 
 Next you create a container app with the NVIDIA GPU Cloud API key.
 
-1. Create the container app.
+1. Create the container app environment.
 
     ```azurecli
     az containerapp env create \
@@ -177,6 +162,9 @@ Next you create a container app with the NVIDIA GPU Cloud API key.
 
     This command returns the URL of your container app. Set this value aside in a text editor for use in a following command.
 
+> [!NOTE]
+> Some NIMs have longer startup times. To account for this, you can configure a [health probe](./health-probes.md) or set your container app's min-replica count with `--min-replicas 1` to keep a replica running at all times.
+
 ## Verify the application works
 
 You can verify a successful deployment by sending a request `POST` request to your application.