Merge branch 'release-ignite-event-hubs-app-groups-ga' of https://github.com/MicrosoftDocs/azure-docs-pr into egriddr0923

Author: spelluru

.openpublishing.redirection.json

@@ -1,5 +1,10 @@
 {
     "redirections": [
+        {
+            "source_path": "articles/iot-hub/iot-hub-rm-template.md",
+            "redirect_url": "articles/iot-hub/iot-hub-rm-rest",
+            "redirect_document_id": false
+        },
         {
             "source_path": "articles/visual-studio/vs-storage-cloud-services-getting-started-blobs.md",
             "redirect_url": "/previous-versions/azure/visual-studio/vs-storage-cloud-services-getting-started-blobs",

articles/active-directory/devices/howto-vm-sign-in-azure-ad-linux.md

@@ -22,7 +22,7 @@ To improve the security of Linux virtual machines (VMs) in Azure, you can integr
 This article shows you how to create and configure a Linux VM and log in with Azure AD by using OpenSSH certificate-based authentication.
 
 > [!IMPORTANT]
-> This capability is now generally available. The previous version that made use of device code flow was [deprecated on August 15, 2021](../../virtual-machines/linux/login-using-aad.md). To migrate from the old version to this version, see the section [Migrate from the previous (preview) version](#migrate-from-the-previous-preview-version).
+> This capability is now generally available. The previous version that made use of device code flow was [deprecated on August 15, 2021](/azure-docs-archive-pr/virtual-machines/linux/login-using-aad). To migrate from the old version to this version, see the section [Migrate from the previous (preview) version](#migrate-from-the-previous-preview-version).
 
 There are many security benefits of using Azure AD with OpenSSH certificate-based authentication to log in to Linux VMs in Azure. They include:
 

articles/active-directory/devices/howto-vm-sign-in-azure-ad-windows.md

@@ -200,7 +200,7 @@ To configure role assignments for your Azure AD-enabled Windows Server 2019 Data
 
 The following example uses [az role assignment create](/cli/azure/role/assignment#az-role-assignment-create) to assign the Virtual Machine Administrator Login role to the VM for your current Azure user. You obtain the username of your current Azure account by using [az account show](/cli/azure/account#az-account-show), and you set the scope to the VM created in a previous step by using [az vm show](/cli/azure/vm#az-vm-show). 
 
-You can also assign the scope at a resource group or subscription level. Normal Azure RBAC inheritance permissions apply. For more information, see [Log in to a Linux virtual machine in Azure by using Azure Active Directory authentication](../../virtual-machines/linux/login-using-aad.md).
+You can also assign the scope at a resource group or subscription level. Normal Azure RBAC inheritance permissions apply. For more information, see [Log in to a Linux virtual machine in Azure by using Azure Active Directory authentication](/azure-docs-archive-pr/virtual-machines/linux/login-using-aad).
 
 ```AzureCLI
 $username=$(az account show --query user.name --output tsv)

articles/active-directory/fundamentals/secure-with-azure-ad-resource-management.md

@@ -310,14 +310,14 @@ When a requirement exists to deploy IaaS workloads to Azure that require identit
 
 ![Diagram that shows Azure AD authentication to Azure VMs.](media/secure-with-azure-ad-resource-management/sign-into-vm.png)
 
-**Supported operating systems**: Signing into virtual machines in Azure using Azure AD authentication is currently supported in Windows and Linux. For more specifics on supported operating systems, refer to the documentation for [Windows](../devices/howto-vm-sign-in-azure-ad-windows.md) and [Linux](../../virtual-machines/linux/login-using-aad.md).
+**Supported operating systems**: Signing into virtual machines in Azure using Azure AD authentication is currently supported in Windows and Linux. For more specifics on supported operating systems, refer to the documentation for [Windows](../devices/howto-vm-sign-in-azure-ad-windows.md) and [Linux](/azure-docs-archive-pr/virtual-machines/linux/login-using-aad).
 
 **Credentials**: One of the key benefits of signing into virtual machines in Azure using Azure AD authentication is the ability to use the same federated or managed Azure AD credentials that you normally use for access to Azure AD services for sign-in to the virtual machine.
 
 >[!NOTE]
 >The Azure AD tenant that is used for sign-in in this scenario is the Azure AD tenant that is associated with the subscription that the virtual machine has been provisioned into. This Azure AD tenant can be one that has identities synchronized from on-premises AD DS. Organizations should make an informed choice that aligns with their isolation principals when choosing which subscription and Azure AD tenant they wish to use for sign-in to these servers.
 
-**Network Requirements**: These virtual machines will need to access Azure AD for authentication so you must ensure that the virtual machines network configuration permits outbound access to Azure AD endpoints on 443. See the documentation for [Windows](../devices/howto-vm-sign-in-azure-ad-windows.md) and [Linux](../../virtual-machines/linux/login-using-aad.md) for more information.
+**Network Requirements**: These virtual machines will need to access Azure AD for authentication so you must ensure that the virtual machines network configuration permits outbound access to Azure AD endpoints on 443. See the documentation for [Windows](../devices/howto-vm-sign-in-azure-ad-windows.md) and [Linux](/azure-docs-archive-pr/virtual-machines/linux/login-using-aad) for more information.
 
 **Role-based Access Control (RBAC)**: Two RBAC roles are available to provide the appropriate level of access to these virtual machines. These RBAC roles can be configured via the Azure AD Portal or via the Azure Cloud Shell Experience. For more information, see [Configure role assignments for the VM](../devices/howto-vm-sign-in-azure-ad-windows.md).
 

articles/azure-arc/data/preview-testing.md

@@ -58,13 +58,13 @@ To install a pre-release version, follow these pre-requisite instructions:
 If you use the Azure CLI extension:
 
 - Uninstall the Azure CLI extension (`az extension remove -n arcdata`).
-- Download the latest pre-release Azure CLI extension `.whl` file from [https://aka.ms/az-cli-arcdata-ext](https://aka.ms/az-cli-arcdata-ext).
+- Download the latest pre-release Azure CLI extension `.whl` file from the link in the [Current preview release information](#Current preview release information)
 - Install the latest pre-release Azure CLI extension (`az extension add -s <location of downloaded .whl file>`).
 
 If you use the Azure Data Studio extension to install:
 
 - Uninstall the Azure Data Studio extension. Select the Extensions panel and select on the **Azure Arc** extension, select **Uninstall**.
-- Download the latest pre-release Azure Data Studio extension .vsix files from [https://aka.ms/ads-arcdata-ext](https://aka.ms/ads-arcdata-ext) and [https://aka.ms/ads-azcli-ext](https://aka.ms/ads-azcli-ext).
+- Download the latest pre-release Azure Data Studio extension .vsix files from the links in the [Current preview release information](#Current preview release information)
 - Install the extensions by choosing File -> Install Extension from VSIX package and then browsing to the download location of the .vsix files. Install the `azcli` extension first and then `arc`.
 
 ### Install using Azure CLI

articles/azure-maps/quick-android-map.md

@@ -4,7 +4,7 @@ titleSuffix:  Microsoft Azure Maps
 description: 'Quickstart: Learn how to create an Android app using the Azure Maps Android SDK.'
 author: stevemunk
 ms.author: v-munksteve
-ms.date: 02/09/2022
+ms.date: 09/22/2022
 ms.topic: quickstart
 ms.service: azure-maps
 services: azure-maps
@@ -120,7 +120,17 @@ The next step in building your application is to install the Azure Maps Android
 
    :::image type="content" source="./media/quick-android-map/project-settings-file.png" alt-text="A screenshot of the project settings file in Android Studio.":::
 
-3. Open the application **build.gradle** file and do the following:
+3. Open the project's **gradle.properties** file, verify that `android.useAndroidX` and `android.enableJetifier` are both set to `true`.
+   
+   If the **gradle.properties** file does not include `android.useAndroidX` and `android.enableJetifier`, add the next two lines to the end of the file:
+   
+   ```gradle
+   android.useAndroidX=true
+   android.enableJetifier=true
+   ```
+   
+
+4. Open the application **build.gradle** file and do the following:
 
     1. Verify your project's **minSdk** is **21** or higher.
 
@@ -143,7 +153,7 @@ The next step in building your application is to install the Azure Maps Android
 
       :::image type="content" source="./media/quick-android-map/build-gradle-file.png" alt-text="A screenshot showing the application build dot gradle file in Android Studio.":::
 
-4. Add a map fragment to the main activity:
+5. Add a map fragment to the main activity:
 
     ```xml
     <com.azure.android.maps.control.MapControl
@@ -159,7 +169,7 @@ The next step in building your application is to install the Azure Maps Android
 
 ::: zone pivot="programming-language-java-android"
 
-5. In the **MainActivity.java** file you'll need to:
+6. In the **MainActivity.java** file you'll need to:
 
     * Add imports for the Azure Maps SDK.
     * Set your Azure Maps authentication information.
@@ -267,7 +277,7 @@ The next step in building your application is to install the Azure Maps Android
 
 ::: zone pivot="programming-language-kotlin"
 
-5. In the **MainActivity.kt** file you'll need to:
+7. In the **MainActivity.kt** file you'll need to:
 
     * add imports for the Azure Maps SDK
     * set your Azure Maps authentication information
@@ -373,7 +383,7 @@ The next step in building your application is to install the Azure Maps Android
 
 ::: zone-end
 
-6. Select the run button from the toolbar, as shown in the following image (or press `Control` + `R` on a Mac), to build your application.
+8. Select the run button from the toolbar, as shown in the following image (or press `Control` + `R` on a Mac), to build your application.
 
     :::image type="content" source="media/quick-android-map/run-app.png" alt-text="A screenshot showing the run button in Android Studio.":::
 

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

@@ -2,7 +2,7 @@
 title: Linter settings for Bicep config
 description: Describes how to customize configuration values for the Bicep linter
 ms.topic: conceptual
-ms.date: 09/21/2022
+ms.date: 09/23/2022
 ---
 
 # Add linter settings in the Bicep config file
@@ -89,6 +89,9 @@ The following example shows the rules that are available for configuration.
         "use-protectedsettings-for-commandtoexecute-secrets": {
           "level": "warning"
         },
+        "use-resource-id-functions": {
+          "level": "warning"
+        },
         "use-stable-resource-identifiers": {
           "level": "warning"
         },

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

@@ -1,11 +1,11 @@
 ---
-title: Linter rule - no hard-coded locations
-description: Linter rule - no hard-coded locations
+title: Linter rule - no hardcoded locations
+description: Linter rule - no hardcoded locations
 ms.topic: conceptual
 ms.date: 1/6/2022
 ---
 
-# Linter rule - no hard-coded locations
+# Linter rule - no hardcoded locations
 
 This rule finds uses of Azure location values that aren't parameterized.
 
@@ -17,9 +17,9 @@ Use the following value in the [Bicep configuration file](bicep-config-linter.md
 
 ## Solution
 
-Template users may have limited access to regions where they can create resources. A hard-coded resource location might block users from creating a resource, thus preventing them from using the template. By providing a location parameter that defaults to the resource group location, users can use the default value when convenient but also specify a different location.
+Template users may have limited access to regions where they can create resources. A hardcoded resource location might block users from creating a resource, thus preventing them from using the template. By providing a location parameter that defaults to the resource group location, users can use the default value when convenient but also specify a different location.
 
-Rather than using a hard-coded string or variable value, use a parameter, the string 'global', or an expression (but not `resourceGroup().location` or `deployment().location`, see [no-loc-expr-outside-params](./linter-rule-no-loc-expr-outside-params.md)). Best practice suggests that to set your resources' locations, your template should have a string parameter named `location`. This parameter may default to the resource group or deployment location (`resourceGroup().location` or `deployment().location`).
+Rather than using a hardcoded string or variable value, use a parameter, the string 'global', or an expression (but not `resourceGroup().location` or `deployment().location`, see [no-loc-expr-outside-params](./linter-rule-no-loc-expr-outside-params.md)). Best practice suggests that to set your resources' locations, your template should have a string parameter named `location`. This parameter may default to the resource group or deployment location (`resourceGroup().location` or `deployment().location`).
 
 The following example fails this test because the resource's `location` property uses a string literal:
 
@@ -61,7 +61,7 @@ The following example fails this test because a string literal is being passed i
 module m1 'module1.bicep' = {
   name: 'module1'
   params: {
-    location: 'westus'    
+    location: 'westus'
   }
 }
 ```

articles/azure-resource-manager/bicep/linter-rule-use-resource-id-functions.md

@@ -0,0 +1,114 @@
+---
+title: Linter rule - use resource ID functions
+description: Linter rule - use resource ID functions
+ms.topic: conceptual
+ms.date: 09/23/2022
+---
+
+# Linter rule - use resource ID functions
+
+Ensures that the ID of a symbolic resource name or a suitable function is used rather than a manually created ID, such as a concatenating string, for all properties representing a resource ID. Use resource symbolic names whenever it's possible.
+
+The allowed functions include:
+
+- [`extensionResourceId`](./bicep-functions-resource.md#extensionresourceid)
+- [`resourceId`](./bicep-functions-resource.md#resourceid)
+- [`subscriptionResourceId`](./bicep-functions-resource.md#subscriptionresourceid)
+- [`tenantResourceId`](./bicep-functions-resource.md#tenantresourceid)
+- [`reference`](./bicep-functions-resource.md#reference)
+- [`subscription`](./bicep-functions-scope.md#subscription)
+- [`guid`](./bicep-functions-string.md#guid)
+
+## Linter rule code
+
+Use the following value in the [Bicep configuration file](bicep-config-linter.md) to customize rule settings:
+
+`use-resource-id-functions`
+
+## Solution
+
+The following example fails this test because the resource's `api/id` property uses a manually created string:
+
+```bicep
+@description('description')
+param connections_azuremonitorlogs_name string
+
+@description('description')
+param location string
+
+@description('description')
+param resourceTags object
+param tenantId string
+
+resource connections_azuremonitorlogs_name_resource 'Microsoft.Web/connections@2016-06-01' = {
+  name: connections_azuremonitorlogs_name
+  location: location
+  tags: resourceTags
+  properties: {
+    displayName: 'azuremonitorlogs'
+    statuses: [
+      {
+        status: 'Connected'
+      }
+    ]
+    nonSecretParameterValues: {
+      'token:TenantId': tenantId
+      'token:grantType': 'code'
+    }
+    api: {
+      name: connections_azuremonitorlogs_name
+      displayName: 'Azure Monitor Logs'
+      description: 'Use this connector to query your Azure Monitor Logs across Log Analytics workspace and Application Insights component, to list or visualize results.'
+      iconUri: 'https://connectoricons-prod.azureedge.net/releases/v1.0.1501/1.0.1501.2507/${connections_azuremonitorlogs_name}/icon.png'
+      brandColor: '#0072C6'
+      id: '/subscriptions/<subscription_id_here>/providers/Microsoft.Web/locations/<region_here>/managedApis/${connections_azuremonitorlogs_name}'
+      type: 'Microsoft.Web/locations/managedApis'
+    }
+  }
+}
+```
+
+You can fix it by using the `subscriptionResourceId()` function:
+
+```bicep
+@description('description')
+param connections_azuremonitorlogs_name string
+
+@description('description')
+param location string
+
+@description('description')
+param resourceTags object
+param tenantId string
+
+resource connections_azuremonitorlogs_name_resource 'Microsoft.Web/connections@2016-06-01' = {
+  name: connections_azuremonitorlogs_name
+  location: location
+  tags: resourceTags
+  properties: {
+    displayName: 'azuremonitorlogs'
+    statuses: [
+      {
+        status: 'Connected'
+      }
+    ]
+    nonSecretParameterValues: {
+      'token:TenantId': tenantId
+      'token:grantType': 'code'
+    }
+    api: {
+      name: connections_azuremonitorlogs_name
+      displayName: 'Azure Monitor Logs'
+      description: 'Use this connector to query your Azure Monitor Logs across Log Analytics workspace and Application Insights component, to list or visualize results.'
+      iconUri: 'https://connectoricons-prod.azureedge.net/releases/v1.0.1501/1.0.1501.2507/${connections_azuremonitorlogs_name}/icon.png'
+      brandColor: '#0072C6'
+      id: subscriptionResourceId('Microsoft.Web/locations/managedApis', location, connections_azuremonitorlogs_name)
+      type: 'Microsoft.Web/locations/managedApis'
+    }
+  }
+}
+```
+
+## Next steps
+
+For more information about the linter, see [Use Bicep linter](./linter.md).

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

@@ -2,7 +2,7 @@
 title: Use Bicep linter
 description: Learn how to use Bicep linter.
 ms.topic: conceptual
-ms.date: 09/21/2022
+ms.date: 9/23/2022
 ---
 
 # Use Bicep linter
@@ -39,6 +39,7 @@ The default set of linter rules is minimal and taken from [arm-ttk test cases](.
 - [secure-secrets-in-params](./linter-rule-secure-secrets-in-parameters.md)
 - [simplify-interpolation](./linter-rule-simplify-interpolation.md)
 - [use-protectedsettings-for-commandtoexecute-secrets](./linter-rule-use-protectedsettings-for-commandtoexecute-secrets.md)
+- [use-resource-id-functions](./linter-rule-use-resource-id-functions.md)
 - [use-stable-resource-identifiers](./linter-rule-use-stable-resource-identifier.md)
 - [use-stable-vm-image](./linter-rule-use-stable-vm-image.md)