Merge pull request #301631 from MicrosoftDocs/main

6/20/2025 AM Publish

Author: Taojunshen

articles/active-directory-b2c/billing.md

@@ -5,7 +5,7 @@ author: kengaderdus
 manager: CelesteDG
 ms.service: azure-active-directory
 ms.topic: reference
-ms.date: 06/10/2025
+ms.date: 06/13/2025
 ms.author: kengaderdus
 ms.subservice: b2c
 ms.custom: fasttrack-edit
@@ -19,7 +19,7 @@ ms.custom: fasttrack-edit
 
 Azure Active Directory B2C (Azure AD B2C) pricing is based on monthly active users (MAU), which is the count of unique users with authentication activity within a calendar month. This billing model applies to both Azure AD B2C tenants and [Microsoft Entra guest user collaboration (B2B)](../active-directory/external-identities/external-identities-pricing.md). MAU billing helps you reduce costs by offering a free tier and flexible, predictable pricing. 
 
-In this article, learn about MAU and Go Local billing, linking Azure AD B2C tenants to a subscription, and changing the pricing tier.
+In this article, learn about MAU and Go Local billing and linking Azure AD B2C tenants to a subscription.
 
 ## MAU overview
 
@@ -43,7 +43,7 @@ MAU billing went into effect for Azure AD B2C tenants on **November 1, 2019**. A
 - If you have an Azure AD B2C tenant that hasn't been linked to a subscription, link it now. 
 - If you have an existing Azure AD B2C tenant that was linked to a subscription before November 1, 2019, upgrade to the monthly active users (MAU) billing model. You can also choose to stay on the per-authentication billing model.
 
-Your Azure AD B2C tenant must also be linked to the appropriate Azure pricing tier based on the features you want to use. Premium features require Azure AD B2C [Premium P1 or P2 pricing](https://azure.microsoft.com/pricing/details/active-directory-b2c/). You might need to upgrade your pricing tier as you use new features. For example, for risk-based Conditional Access policies, you’ll need to select the Azure AD B2C Premium P2 pricing tier for your tenant.
+Your Azure AD B2C tenant must also be linked to the appropriate Azure pricing tier based on the features you want to use. Premium features require Azure AD B2C [Premium P1 pricing](https://azure.microsoft.com/pricing/details/active-directory-b2c/).
 
 > [!NOTE]
 > Your first 50,000 MAUs per month are free for both Premium P1 and Premium P2 features, but the **free tier doesn’t apply to free trial, credit-based, or sponsorship subscriptions**. Once the free trial period or credits expire for these types of subscriptions, you'll begin to be charged for Azure AD B2C MAUs. To determine the total number of MAUs, we combine MAUs from all your tenants (both Microsoft Entra ID and Azure AD B2C) that are linked to the same subscription.

articles/api-management/TOC.yml

@@ -113,7 +113,7 @@
         href: inject-vnet-v2.md
       - name: Virtual network integration (v2 tiers)
         href: integrate-vnet-outbound.md
-    - name: Virtual network integration (workspace gateway) - requirements
+    - name: Virtual network for workspace gateways
       href: virtual-network-workspaces-resources.md
     - name: Connect privately using private endpoint
       href: private-endpoint.md

articles/api-management/inject-vnet-v2.md

@@ -103,12 +103,7 @@ When you [create](get-started-create-service-instance.md) a Premium v2 instance
 
 When a Premium v2 API Management instance is injected in a virtual network, you have to manage your own DNS to enable inbound access to API Management. 
 
-While you have the option to use your own custom DNS server, we recommend:
-
-1. Configure an Azure [DNS private zone](../dns/private-dns-overview.md).
-1. Link the Azure DNS private zone to the virtual network. 
-
-Learn how to [set up a private zone in Azure DNS](../dns/private-dns-getstarted-portal.md).
+[!INCLUDE [api-management-virtual-network-dns-resolver](../../includes/api-management-virtual-network-dns-resolver.md)]
 
 ### Endpoint access on default hostname
 

articles/api-management/virtual-network-workspaces-resources.md

@@ -1,11 +1,11 @@
 ---
-title: Azure API Management workspace gateways - VNet integration - network resources
+title: Azure API Management workspace gateways - virtual network requirements
 description: Learn about requirements for network resources when you integrate or inject your API Management workspace gateway in an Azure virtual network.
 author: dlepow
 
 ms.service: azure-api-management
 ms.topic: concept-article
-ms.date: 06/03/2025
+ms.date: 06/18/2025
 ms.author: danlep
 ---
 
@@ -91,13 +91,7 @@ Configure other NSG rules to meet your organization's network access requirement
 
 For virtual network injection, you have to manage your own DNS to enable inbound access to your workspace gateway. 
 
-We recommend:
-
-1. Configure an Azure [DNS private zone](../dns/private-dns-overview.md).
-1. Link the Azure DNS private zone to the VNet into which you've deployed your workspace gateway. 
-
-Learn how to [set up a private zone in Azure DNS](../dns/private-dns-getstarted-portal.md).
-
+[!INCLUDE [api-management-virtual-network-dns-resolver](../../includes/api-management-virtual-network-dns-resolver.md)]
 
 ### Access on default hostname
 
@@ -108,9 +102,9 @@ When you create an API Management workspace, the workspace gateway is assigned a
 
 ### Configure DNS record
 
-Create an A record in your DNS server to access the workspace from within your VNet. Map the endpoint record to the private VIP address of your workspace gateway.
+Create an A record in your DNS server to access the workspace from within your virtual network. Map the endpoint record to the private VIP address of your workspace gateway.
 
-For testing purposes, you might update the hosts file on a virtual machine in a subnet connected to the VNet in which API Management is deployed. Assuming the private virtual IP address for your workspace gateway is 10.1.0.5, you can map the hosts file as shown in the following example. The hosts mapping file is at  `%SystemDrive%\drivers\etc\hosts` (Windows) or `/etc/hosts` (Linux, macOS). 
+For testing purposes, you might update the hosts file on a virtual machine in a subnet connected to the virtual network in which API Management is deployed. Assuming the private virtual IP address for your workspace gateway is 10.1.0.5, you can map the hosts file as shown in the following example. The hosts mapping file is at  `%SystemDrive%\drivers\etc\hosts` (Windows) or `/etc/hosts` (Linux, macOS). 
 
 | Internal virtual IP address | Gateway hostname |
 | ----- | ----- |

articles/automation/shared-resources/modules.md

@@ -21,10 +21,10 @@ author: jasminemehndir
 
 Azure Automation uses a number of PowerShell modules to enable cmdlets in runbooks and DSC resources in DSC configurations. Supported modules include:
 
-* [Azure PowerShell Az.Automation](/powershell/azure/new-azureps-module-az).
+* [Azure PowerShell Az modules](/powershell/azure/new-azureps-module-az).
 * Other PowerShell modules.
-* Internal `Orchestrator.AssetManagement.Cmdlets` module.
-* Python 2 modules.
+* Internal `Orchestrator.AssetManagement.Cmdlets` module (not available on a Linux Hybrid Runbook Worker).
+* Python 2 and Python 3 modules.
 * Custom modules that you create.
 
 When you create an Automation account, Azure Automation imports some modules by default. See [Default modules](#default-modules).

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

@@ -3,7 +3,7 @@ title: Linter settings for Bicep config
 description: Describes how to customize configuration values for the Bicep linter
 ms.topic: conceptual
 ms.custom: devx-track-bicep
-ms.date: 04/28/2025
+ms.date: 06/19/2025
 ---
 
 # Add linter settings in the Bicep config file
@@ -37,19 +37,19 @@ The following example shows the rules that are available for configuration.
           "level": "off"
         },
         "max-asserts": {
-          "level": "warning"
+          "level": "error"
         },
         "max-outputs": {
-          "level": "warning"
+          "level": "error"
         },
         "max-params": {
-          "level": "warning"
+          "level": "error"
         },
         "max-resources": {
-          "level": "warning"
+          "level": "error"
         },
         "max-variables": {
-          "level": "warning"
+          "level": "error"
         },
         "nested-deployment-template-scoping": {
           "level": "error"
@@ -115,11 +115,11 @@ The following example shows the rules that are available for configuration.
           "level": "warning"
         },
         "use-recent-api-versions": {
-          "level": "warning",
+          "level": "off",
           "maxAllowedAgeInDays": 730
         },
         "use-recent-module-versions": {
-          "level": "warning"
+          "level": "off"
         },
         "use-resource-id-functions": {
           "level": "off"
@@ -140,7 +140,7 @@ The following example shows the rules that are available for configuration.
           "level": "warning"
         },
         "what-if-short-circuiting": {
-          "level": "warning"
+          "level": "off"
         }
       }
     }

articles/azure-resource-manager/bicep/linter-rule-admin-username-should-not-be-literal.md

@@ -23,6 +23,8 @@ Don't use a literal value or an expression that evaluates to a literal value. In
 The following example fails this test because the user name is a literal value.
 
 ```bicep
+param location string = resourceGroup().location
+
 resource vm 'Microsoft.Compute/virtualMachines@2023-03-01' = {
   name: 'name'
   location: location
@@ -37,6 +39,8 @@ resource vm 'Microsoft.Compute/virtualMachines@2023-03-01' = {
 The next example fails this test because the expression evaluates to a literal value when the default value is used.
 
 ```bicep
+param location string = resourceGroup().location
+
 var defaultAdmin = 'administrator'
 resource vm 'Microsoft.Compute/virtualMachines@2023-03-01' = {
   name: 'name'
@@ -54,7 +58,8 @@ This example passes this test.
 ```bicep
 @secure()
 param adminUsername string
-param location string
+param location string = resourceGroup().location
+
 resource vm 'Microsoft.Compute/virtualMachines@2023-03-01' = {
   name: 'name'
   location: location

articles/azure-resource-manager/bicep/linter-rule-explicit-values-for-loc-params.md

@@ -3,13 +3,16 @@ title: Linter rule - use explicit values for module location parameters
 description: Linter rule - use explicit values for module location parameters.
 ms.topic: reference
 ms.custom: devx-track-bicep
-ms.date: 02/12/2025
+ms.date: 06/19/2025
 ---
 
 # Linter rule - use explicit values for module location parameters
 
 This rule finds module parameters that are used for resource locations and may inadvertently default to an unexpected value.
 
+> [!NOTE]
+> This rule is off by default. Change the level in [bicepconfig.json](./bicep-config-linter.md) to enable it.
+
 ## Linter rule code
 
 Use the following value in the [Bicep configuration file](bicep-config-linter.md) to customize rule settings:

articles/azure-resource-manager/bicep/linter-rule-no-hardcoded-location.md

@@ -3,13 +3,16 @@ title: Linter rule - no hardcoded locations
 description: Linter rule - no hardcoded locations
 ms.topic: reference
 ms.custom: devx-track-bicep
-ms.date: 02/12/2025
+ms.date: 06/19/2025
 ---
 
 # Linter rule - no hardcoded locations
 
 This rule finds uses of Azure location values that aren't parameterized.
 
+> [!NOTE]
+> This rule is off by default. Change the level in [bicepconfig.json](./bicep-config-linter.md) to enable it.
+
 ## Linter rule code
 
 Use the following value in the [Bicep configuration file](bicep-config-linter.md) to customize rule settings:
@@ -25,18 +28,29 @@ Rather than using a hardcoded string or variable value, use a parameter, the str
 The following example fails this test because the resource's `location` property uses a string literal:
 
 ```bicep
-  resource stg 'Microsoft.Storage/storageAccounts@2023-04-01' = {
-      location: 'westus'
+resource stg 'Microsoft.Storage/storageAccounts@2024-01-01' = {
+  name: 'stg'
+  location: 'westus'
+  kind: 'StorageV2'
+  sku: {
+    name: 'Premium_LRS'
   }
+}
 ```
 
 You can fix it by creating a new `location` string parameter (which may optionally have a default value - resourceGroup().location is frequently used as a default):
 
 ```bicep
-  param location string = resourceGroup().location
-  resource stg 'Microsoft.Storage/storageAccounts@2023-04-01' = {
-      location: location
+param location string = resourceGroup().location
+
+resource stg 'Microsoft.Storage/storageAccounts@2023-04-01' = {
+  name: 'stg${uniqueString(resourceGroup().id)}'
+  location: location
+  kind: 'StorageV2'
+  sku: {
+    name: 'Premium_LRS'
   }
+}
 ```
 
 Use **Quick Fix** to create a location parameter and replace the string literal with the parameter name. See the following screenshot:
@@ -46,19 +60,19 @@ Use **Quick Fix** to create a location parameter and replace the string literal
 The following example fails this test because the resource's `location` property uses a variable with a string literal.
 
 ```bicep
-  var location = 'westus'
-  resource stg 'Microsoft.Storage/storageAccounts@2023-04-01' = {
-      location: location
-  }
+var location = 'westus'
+resource stg 'Microsoft.Storage/storageAccounts@2023-04-01' = {
+  location: location
+}
 ```
 
 You can fix it by turning the variable into a parameter:
 
 ```bicep
-  param location string = 'westus'
-  resource stg 'Microsoft.Storage/storageAccounts@2023-04-01' = {
-      location: location
-  }
+param location string = 'westus'
+resource stg 'Microsoft.Storage/storageAccounts@2023-04-01' = {
+    location: location
+}
 ```
 
 The following example fails this test because a string literal is being passed in to a module parameter that is in turn used for a resource's `location` property:

articles/azure-resource-manager/bicep/linter-rule-no-loc-expr-outside-params.md

@@ -3,13 +3,16 @@ title: Linter rule - no location expressions outside of parameter default values
 description: Linter rule - no location expressions outside of parameter default values
 ms.topic: reference
 ms.custom: devx-track-bicep
-ms.date: 02/12/2025
+ms.date: 06/19/2025
 ---
 
 # Linter rule - no location expressions outside of parameter default values
 
 This rule finds `resourceGroup().location` or `deployment().location` used outside of a parameter default value.
 
+> [!NOTE]
+> This rule is off by default. Change the level in [bicepconfig.json](./bicep-config-linter.md) to enable it.
+
 ## Linter rule code
 
 Use the following value in the [Bicep configuration file](bicep-config-linter.md) to customize rule settings: