Merge pull request #2736 from MicrosoftDocs/main

Auto Publish – main to live - 2026-04-14 22:08 UTC

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

articles/defender-for-cloud/ai-model-security.md

@@ -2,13 +2,16 @@
 title: Discover AI models
 description: Learn about AI model security in Microsoft Defender for Cloud.
 ms.topic: concept-article
-ms.date: 03/25/2026
+ms.date: 04/14/2026
 ms.author: elkrieger
 zone_pivot_groups: defender-portal-experience
 ---
 
 # AI model security
 
+> [!IMPORTANT]
+> This feature is currently in preview and included with the Microsoft Defender for AI Services plan. During preview, there is no additional charge for AI model scanning. However, enabling the Defender for AI Services plan may incur costs related to threat protection features. Continued inclusion of AI model scanning feature as part of Defender for AI Services is not guaranteed when it becomes generally available (GA), and licensing requirements may change. If that occurs, a notification will be sent before the feature is disabled with options to re‑enable it under the applicable license.
+
 As organizations increasingly use artificial intelligence (AI) models to drive automation, insights, and intelligent decision-making, security teams need visibility and control to assess the safety and compliance of AI models entering their environments. These models often have broad access to data and infrastructure. Without these capabilities, it becomes increasingly difficult to enforce internal standards. 
 
 Microsoft Defender for Cloud's Defender for AI security supports AI model scanning. AI model scanning provides proactive detection of unsafe or malicious artifacts and continuously monitors models for risk throughout the AI lifecycle.

articles/key-vault/managed-hsm/quick-create-cli.md

@@ -6,7 +6,7 @@ author: msmbaldwin
 ms.service: azure-key-vault
 ms.subservice: managed-hsm
 ms.topic: quickstart
-ms.date: 03/30/2026
+ms.date: 04/14/2026
 ms.author: mbaldwin
 ms.custom: mode-api, devx-track-azurecli 
 ms.devlang: azurecli
@@ -31,11 +31,7 @@ You also need:
 
 ## Create a resource group
 
-A resource group is a logical container into which you deploy and manage Azure resources. The following example creates a resource group named `<resource-group>` in the `<location>` location.
-
-```azurecli-interactive
-az group create --name "<resource-group>" --location <location>
-```
+[!INCLUDE [Create a resource group](~/reusable-content/ce-skilling/azure/includes/create-resource-group-cli.md)]
 
 ## Create a Managed HSM
 
@@ -48,15 +44,20 @@ Creating a Managed HSM is a two-step process:
 Use the `az keyvault create` command to create a Managed HSM. This script has three mandatory parameters: a resource group name, an HSM name, and the geographic location.
 
 To create a Managed HSM resource, provide the following inputs:
-- A resource group where you place the Managed HSM in your subscription.
-- An Azure location.
+- Managed HSM name: A string of 3 to 24 characters that can contain only numbers (0-9), letters (a-z, A-Z), and hyphens (-).
+
+  > [!Important]
+  > Each Managed HSM must have a unique name. Replace `<hsm-name>` with your own unique Managed HSM name in the following examples.
+
+- Resource group name: **myResourceGroup**.
+- Location: **EastUS**.
 - A list of initial administrators.
 
-The following example creates an HSM named `<hsm-name>` in the resource group `<resource-group>`, residing in the specified location, with **the current signed in user** as the only administrator, and a **7-day retention period** for soft-delete. You continue to pay for the Managed HSM until it's purged in a **soft-delete period**. For more information, see [Managed HSM soft-delete and purge protection](recovery.md#what-are-soft-delete-and-purge-protection) and read more about [Managed HSM soft-delete](soft-delete-overview.md).
+The following example creates an HSM named `<hsm-name>` in the resource group *myResourceGroup*, residing in the *EastUS* location, with **the current signed in user** as the only administrator, and a **7-day retention period** for soft-delete. You continue to pay for the Managed HSM until it's purged in a **soft-delete period**. For more information, see [Managed HSM soft-delete and purge protection](recovery.md#what-are-soft-delete-and-purge-protection) and read more about [Managed HSM soft-delete](soft-delete-overview.md).
 
 ```azurecli-interactive
 oid=$(az ad signed-in-user show --query id -o tsv)
-az keyvault create --hsm-name "<hsm-name>" --resource-group "<resource-group>" --location "<location>" --administrators $oid --retention-days 7
+az keyvault create --hsm-name "<hsm-name>" --resource-group "myResourceGroup" --location "EastUS" --administrators $oid --retention-days 7
 ```
 
 > [!NOTE]
@@ -90,13 +91,7 @@ az keyvault security-domain download --hsm-name <hsm-name> --sd-wrapping-keys ./
 
 ## Clean up resources
 
-Other quickstarts and tutorials in this collection build upon this quickstart. If you plan to continue on to work with subsequent quickstarts and tutorials, you may wish to leave these resources in place.
-
-When no longer needed, you can use the [az group delete](/cli/azure/group) command to remove the resource group, and all related resources. You can delete the resources as follows:
-
-```azurecli-interactive
-az group delete --name <resource-group>
-```
+[!INCLUDE [Delete resource group](~/reusable-content/ce-skilling/azure/includes/delete-resource-group-cli.md)]
 [!INCLUDE [Managed HSM cleanup warning](~/reusable-content/ce-skilling/azure/includes/managed-hsm/cleanup-warning.md)]
 
 ## Next steps

articles/key-vault/managed-hsm/quick-create-powershell.md

@@ -3,7 +3,7 @@ title: Create and retrieve attributes of a managed key in Azure Key Vault – Az
 description: Quickstart showing how to set and retrieve a managed key from Azure Key Vault using Azure PowerShell
 author: msmbaldwin
 ms.author: mbaldwin
-ms.date: 03/30/2026
+ms.date: 04/14/2026
 ms.topic: quickstart
 ms.service: azure-key-vault
 ms.subservice: keys
@@ -22,11 +22,7 @@ If you don't have an Azure subscription, create a [free account](https://azure.m
 
 ## Create a resource group
 
-A resource group is a logical container into which you deploy and manage Azure resources. Use the Azure PowerShell [New-AzResourceGroup](/powershell/module/az.resources/new-azresourcegroup) cmdlet to create a resource group named `<resource-group>` in the `<location>` location. 
-
-```azurepowershell-interactive
-New-AzResourceGroup -Name "<resource-group>" -Location "<location>"
-```
+[!INCLUDE [Create a resource group](~/reusable-content/ce-skilling/azure/includes/create-resource-group-powershell.md)]
 
 ## Get your principal ID
 
@@ -53,12 +49,12 @@ Use the Azure PowerShell [New-AzKeyVaultManagedHsm](/powershell/module/az.keyvau
   > [!Important]
   > Each Managed HSM must have a unique name. Replace `<hsm-name>` with your own unique Managed HSM name in the following examples.
 
-- Resource group name: `<resource-group>`.
-- Location: Your selected location.
+- Resource group name: *myResourceGroup*.
+- Location: *EastUS* (or your selected location).
 - Your principal ID: Pass the Microsoft Entra principal ID that you obtained in the last section to the "Administrator" parameter. 
 
 ```azurepowershell-interactive
-New-AzKeyVaultManagedHsm -Name "<hsm-name>" -ResourceGroupName "<resource-group>" -Location "<location>" -Administrator "<principal-id>" -SoftDeleteRetentionInDays "<retention-days>"
+New-AzKeyVaultManagedHsm -Name "<hsm-name>" -ResourceGroupName "myResourceGroup" -Location "EastUS" -Administrator "<principal-id>" -SoftDeleteRetentionInDays "<retention-days>"
 ```
 > [!NOTE]
 > The create command can take a few minutes. When it returns successfully, you're ready to activate your HSM.