Merge pull request #301059 from MicrosoftDocs/main

6/9/2025 AM Publish

Author: Taojunshen

articles/active-directory-b2c/identity-provider-adfs.md

@@ -31,7 +31,7 @@ zone_pivot_groups: b2c-policy-type
 
 To enable sign-in for users with an AD FS account in Azure Active Directory B2C (Azure AD B2C), create an Application Group in your AD FS. For more information, see [Build a web application using OpenID Connect with AD FS 2016 and later](../active-directory/develop/msal-migration.md)
 
-To create an Application Group, follow theses steps:
+To create an Application Group, follow these steps:
 
 1. In **Server Manager**, select **Tools**, and then select **AD FS Management**.
 1. In AD FS Management, right-click on **Application Groups** and select **Add Application Group**.

articles/api-management/llm-semantic-cache-lookup-policy.md

@@ -68,6 +68,9 @@ Use the `llm-semantic-cache-lookup` policy to perform cache lookup of responses
 - This policy can only be used once in a policy section.
 - Fine-tune the value of `score-threshold` based on your application to ensure that the right sensitivity is used when determining which queries to cache. Start with a low value such as 0.05 and adjust to optimize the ratio of cache hits to misses.
 - The embeddings model should have enough capacity and sufficient context size to accommodate the prompt volume and prompts.
+- Score threshold above 0.2 may lead to cache mismatch. Consider using lower value for sensitive use cases.
+- Control cross-user access to cache entries by specifying `vary-by`with specific user or user-group identifiers.
+- Consider adding [llm-content-safety](./llm-content-safety-policy.md) policy with prompt shield to protect from prompt attacks.
 
 
 ## Examples

articles/azure-resource-manager/bicep/bicep-config-linter.md

@@ -75,6 +75,9 @@ The following example shows the rules that are available for configuration.
         "no-unused-existing-resources": {
           "level": "warning"
         },
+        "no-unused-imports": {
+          "level": "warning"
+        },
         "no-unused-params": {
           "level": "warning"
         },

articles/azure-resource-manager/bicep/bicep-core-diagnostics.md

@@ -7,7 +7,7 @@ ms.custom:
   - devx-track-bicep
   - devx-track-arm-template
   - build-2025
-ms.date: 05/20/2025
+ms.date: 06/06/2025
 ---
 
 # Bicep core diagnostics

articles/azure-resource-manager/bicep/deployment-stacks.md

@@ -3,7 +3,7 @@ title: Create and deploy Azure deployment stacks in Bicep
 description: Understand how to create deployment stacks in Bicep.
 ms.topic: how-to
 ms.custom: devx-track-azurecli, devx-track-azurepowershell, devx-track-bicep
-ms.date: 03/25/2025
+ms.date: 06/09/2025
 ---
 
 # Create and deploy Azure deployment stacks in Bicep
@@ -31,6 +31,8 @@ Deployment stacks provide the following benefits:
 
 ### Known limitations
 
+- There is a limit of 800 deployment stacks that can be created within a single scope.
+- A maximum of 2,000 Deny Assignments can exist at any given scope.
 - The deployment stack doesn't manage implicitly created resources. Therefore, you can't use [deny-assignments](../../role-based-access-control/deny-assignments.md) or cleanup for these resources.
 - Deny-assignments don't support tags.
 - Deny-assignments aren't supported at the management group scope. However, they're supported in a management group stack if the deployment is pointed at the subscription scope.

articles/azure-resource-manager/bicep/linter-rule-no-unused-imports.md

@@ -0,0 +1,46 @@
+---
+title: Linter rule - no unused imports
+description: Linter rule - no unused imports
+ms.topic: reference
+ms.custom: devx-track-bicep
+ms.date: 06/06/2025
+---
+
+# Linter rule - no unused imports
+
+This rule finds [import alias](./bicep-import.md#import-variables-types-and-functions) that aren't referenced anywhere in the Bicep file.
+
+## Linter rule code
+
+Use the following value in the [Bicep configuration file](bicep-config-linter.md) to customize rule settings:
+
+`no-unused-imports`
+
+## Solution
+
+To reduce confusion in your Bicep file, delete any imports that are defined but not used. This test finds all imports that aren't used anywhere in the template.
+
+The following example fails this test because `myImports` and `myObjectType` are not used in the Bicep file:
+
+```bicep
+import * as myImports from 'exports.bicep'
+import {myObjectType, sayHello} from 'exports.bicep'
+
+output greeting string = sayHello('Bicep user')
+```
+
+You can fix it by removing and updating the `import` statements.
+
+```bicep
+import {sayHello} from 'exports.bicep'
+
+output greeting string = sayHello('Bicep user')
+```
+
+Use **Quick Fix** to remove the unused imports:
+
+:::image type="content" source="./media/linter-rule-no-unused-imports/linter-rule-no-unused-imports-quick-fix.png" alt-text="A screenshot of using Quick Fix for the no-unused-variables linter rule.":::
+
+## Next steps
+
+For more information about the linter, see [Use Bicep linter](./linter.md).

articles/azure-resource-manager/bicep/linter.md

@@ -3,7 +3,7 @@ title: Use Bicep linter
 description: Learn how to use Bicep linter.
 ms.topic: how-to
 ms.custom: devx-track-bicep
-ms.date: 02/12/2025
+ms.date: 06/06/2025
 ---
 
 # Use Bicep linter
@@ -35,6 +35,7 @@ The default set of linter rules is minimal and taken from [arm-ttk test cases](.
 - [no-loc-expr-outside-params](./linter-rule-no-loc-expr-outside-params.md)
 - [no-unnecessary-dependson](./linter-rule-no-unnecessary-dependson.md)
 - [no-unused-existing-resources](./linter-rule-no-unused-existing-resources.md)
+- [no-unused-imports](./linter-rule-no-unused-imports.md)
 - [no-unused-params](./linter-rule-no-unused-parameters.md)
 - [no-unused-vars](./linter-rule-no-unused-variables.md)
 - [outputs-should-not-contain-secrets](./linter-rule-outputs-should-not-contain-secrets.md)
@@ -57,7 +58,7 @@ The default set of linter rules is minimal and taken from [arm-ttk test cases](.
 - [use-stable-vm-image](./linter-rule-use-stable-vm-image.md)
 - [what-if-short-circuiting](./linter-rule-what-if-short-circuiting.md)
 
-You can customize how the linter rules are applied. To overwrite the default settings, add a **bicepconfig.json** file and apply custom settings. For more information about applying those settings, see [Add custom settings in the Bicep config file](bicep-config-linter.md).
+You can enable or disable all linter rules and control how they are applied using a configuration file. To override the default behavior, create a **bicepconfig.json** file with your custom settings. For more information about applying those settings, see [Add custom settings in the Bicep config file](bicep-config-linter.md).
 
 ## Use in Visual Studio Code
 

articles/azure-resource-manager/bicep/media/linter-rule-no-unused-imports/linter-rule-no-unused-imports-quick-fix.png

@@ -509,6 +509,9 @@ items:
       - name: No unused existing resources
         displayName: linter
         href: linter-rule-no-unused-existing-resources.md
+      - name: No unused imports
+        displayName: linter
+        href: linter-rule-no-unused-imports.md
       - name: No unused parameters
         displayName: linter
         href: linter-rule-no-unused-parameters.md

articles/azure-resource-manager/bicep/toc.yml

@@ -10,7 +10,10 @@ ms.custom: engagement-fy23
 
 # Install Cloud Backup for Virtual Machines (preview)
 
-Cloud Backup for Virtual Machines is a plug-in installed in the Azure VMware Solution and enables you to back up and restore Azure NetApp Files datastores and virtual machines (VMs). 
+Cloud Backup for Virtual Machines is a plug-in installed in the Azure VMware Solution and enables you to back up and restore Azure NetApp Files datastores and virtual machines (VMs) residing in NetApp Datastore to be backed up and restored.
+
+:::image type="content" source="./media/cloud-backup/cloud-backup-overview.png" alt-text="Diagram showing solution overview of Cloud Backup for Virtual Machines." lightbox="./media/cloud-backup/cloud-backup-overview.png":::
+
 
 Cloud Backup for Virtual Machines features:
 
@@ -96,7 +99,7 @@ You can execute the run command to uninstall Cloud Backup for Virtual Machines.
 
 > [!IMPORTANT]
 > Before you initiate the upgrade, you must:
-> * Backup the MySQL database of Cloud Backup for Virtual Machines. 
+> * Back up the MySQL database of Cloud Backup for Virtual Machines. 
 > * Ensure that there are no other VMs installed in the VMware vSphere tag: `AVS_ANF_CLOUD_ADMIN_VM_TAG`. All VMs with this tag are deleted when you uninstall.
 
 1. Select **Run command** > **Packages** > **NetApp.CBS.AVS** > **Uninstall-NetAppCBSAppliance**.