Merge branch 'master' of https://github.com/MicrosoftDocs/azure-docs-pr into rolyon-abac-principal-attributes-updates

Author: rolyon

articles/azure-monitor/insights/sql-insights-enable.md

@@ -154,7 +154,7 @@ When settings up your profile for SQL monitoring, you will need one of the follo
 If you have these permissions, a new Key Vault access policy will be automatically created as part of creating your SQL Monitoring profile that uses the Key Vault you specified. 
 
 > [!IMPORTANT]
-> You need to ensure that network and security configuration allows the monitoring VM to access Key Vault. For more information, see [Access Azure Key Vault behind a firewall](/key-vault/general/access-behind-firewall.md) and [Configure Azure Key Vault networking settings](/key-vault/general/how-to-azure-key-vault-network-security.md).
+> You need to ensure that network and security configuration allows the monitoring VM to access Key Vault. For more information, see [Access Azure Key Vault behind a firewall](/azure/key-vault/general/access-behind-firewall) and [Configure Azure Key Vault networking settings](/azure/key-vault/general/how-to-azure-key-vault-network-security).
 
 ## Create SQL monitoring profile
 Open SQL insights by selecting **SQL (preview)** from the **Insights** section of the **Azure Monitor** menu in the Azure portal. Click **Create new profile**. 

articles/azure-monitor/insights/sql-insights-troubleshoot.md

@@ -186,7 +186,7 @@ During preview of SQL Insights, you may encounter the following known issues.
 
 ## Best practices
 
-* **Ensure access to Key Vault from the monitoring VM**. If you use Key Vault to store SQL authentication passwords (strongly recommended), you need to ensure that network and security configuration allows the monitoring VM to access Key Vault. For more information, see [Access Azure Key Vault behind a firewall](/key-vault/general/access-behind-firewall.md) and [Configure Azure Key Vault networking settings](/key-vault/general/how-to-azure-key-vault-network-security.md). To verify that the monitoring VM can access Key Vault, you can execute the following commands from an SSH session connected to the VM. You should be able to successfully retrieve the access token and the secret. Replace `[YOUR-KEY-VAULT-URL]`, `[YOUR-KEY-VAULT-SECRET]`, and `[YOUR-KEY-VAULT-ACCESS-TOKEN]` with actual values.
+* **Ensure access to Key Vault from the monitoring VM**. If you use Key Vault to store SQL authentication passwords (strongly recommended), you need to ensure that network and security configuration allows the monitoring VM to access Key Vault. For more information, see [Access Azure Key Vault behind a firewall](/azure/key-vault/general/access-behind-firewall) and [Configure Azure Key Vault networking settings](/azure/key-vault/general/how-to-azure-key-vault-network-security). To verify that the monitoring VM can access Key Vault, you can execute the following commands from an SSH session connected to the VM. You should be able to successfully retrieve the access token and the secret. Replace `[YOUR-KEY-VAULT-URL]`, `[YOUR-KEY-VAULT-SECRET]`, and `[YOUR-KEY-VAULT-ACCESS-TOKEN]` with actual values.
 
   ```bash
   # Get an access token for accessing Key Vault secrets

articles/azure-monitor/logs/cross-workspace-query.md

@@ -26,7 +26,7 @@ There are two methods to query data that is stored in multiple workspace and app
 
 * The number of Application Insights resources and Log Analytics workspaces that you can include in a single query is limited to 100.
 * Cross-resource query is not supported in View Designer. You can Author a query in Log Analytics and pin it to Azure dashboard to [visualize a log query](../visualize/tutorial-logs-dashboards.md) or include in [Workbooks](../visualize/workbooks-overview.md).
-* Cross-resource queries in log alerts are only supported in the current [scheduledQueryRules API](/rest/api/monitor/scheduledqueryrules). If you're using the legacy Log Analytics Alerts API, you'll need to [switch to the current API](../alerts/alerts-log-api-switch.md).
+* Cross-resource queries in log alerts are only supported in the current [scheduledQueryRules API](/rest/api/monitor/scheduledqueryrule-2018-04-16/scheduled-query-rules). If you're using the legacy Log Analytics Alerts API, you'll need to [switch to the current API](../alerts/alerts-log-api-switch.md).
 
 
 ## Querying across Log Analytics workspaces and from Application Insights
@@ -141,4 +141,4 @@ applicationsScoping
 
 ## Next steps
 
-- Review [Analyze log data in Azure Monitor](./log-query-overview.md) for an overview of log queries and how Azure Monitor log data is structured.
+- Review [Analyze log data in Azure Monitor](./log-query-overview.md) for an overview of log queries and how Azure Monitor log data is structured.

articles/azure-monitor/logs/unify-app-resource-data.md

@@ -53,7 +53,7 @@ The query uses Application Insights schema, although the query is executed in th
 ![Cross-query results example](media/unify-app-resource-data/app-insights-query-results.png)
 
 >[!NOTE]
->[Cross-resource queries](../logs/cross-workspace-query.md) in log alerts are only supported in the current [scheduledQueryRules API](/rest/api/monitor/scheduledqueryrules). If you're using the legacy Log Analytics Alerts API, you'll need to [switch to the current API](../alerts/alerts-log-api-switch.md). [See example templates](../alerts/alerts-log-create-templates.md).
+>[Cross-resource queries](../logs/cross-workspace-query.md) in log alerts are only supported in the current [scheduledQueryRules API](/rest/api/monitor/scheduledqueryrule-2018-04-16/scheduled-query-rules). If you're using the legacy Log Analytics Alerts API, you'll need to [switch to the current API](../alerts/alerts-log-api-switch.md). [See example templates](../alerts/alerts-log-create-templates.md).
 
 ## Application Insights and Log Analytics workspace schema differences
 The following table shows the schema differences between Log Analytics and Application Insights.  

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

@@ -334,6 +334,7 @@ The preceding example is equivalent to the following JSON.
 
 - No support for the concept of apiProfile, which is used to map a single apiProfile to a set apiVersion for each resource type.
 - No support for user-defined functions.
+- Some Bicep features require a corresponding change to the intermediate language (Azure Resource Manager JSON templates). We announce these features as available when all of the required updates have been deployed to global Azure. If you're using a different environment, such as Azure Stack, there may be a delay in the availability of the feature. The Bicep feature is only available when the intermediate language has also been updated in that environment.
 
 ## Next steps
 

articles/communication-services/concepts/known-issues.md

@@ -26,12 +26,12 @@ The following sections provide information about known issues associated with th
 
 iOS 15.1 introduced a bug that affects the majority of Communication Services calls with video that are placed in iOS with Safari. Specifically, the problem occurs when a user joins a Communication Services call or a meeting in Microsoft Teams by using Communication Services on iOS 15.1 on any browser with video turned on. This set of circumstances causes the Safari browser to crash.
 
-We managed to bypass that bug, now users will be able to join calls with video on iOS 15.1 also with two limitations:
+We managed to bypass that bug and now users will be able to join calls with video on iOS 15.1 but that uncovered other issues with Webkit.
 
 * Orientation on the receiver's end won't be correct. Mitigation: Switch device orientation to horizontal.
 * Going to background will refresh user's call. Mitigation: Stop video before going to background.
 
-This is a [known bug on iOS 15.1 with Safari](https://bugs.webkit.org/show_bug.cgi?id=231505). You should prevent users from using (turning on) any video when using iOS 15.1 with Safari for Communication Services video calls. You should also prevent this activity for video call meetings between Microsoft Teams and Communication Services.
+This is a [known bug on iOS 15.1 with Safari](https://bugs.webkit.org/show_bug.cgi?id=231505).
 
 ### Refreshing a page doesn't immediately remove the user from their call
 

articles/cosmos-db/mongodb/how-to-provision-throughput-mongodb.md

@@ -4,7 +4,7 @@ description: Learn how to provision container, database, and autoscale throughpu
 ms.service: cosmos-db
 ms.subservice: cosmosdb-mongo
 ms.topic: how-to
-ms.date: 08/26/2021
+ms.date: 11/17/2021
 author: gahl-levy
 ms.author: gahllevy
 ms.custom: devx-track-js, devx-track-azurecli, devx-track-csharp
@@ -27,14 +27,14 @@ If you are using a different API, see [SQL API](../how-to-provision-container-th
 
    * Indicate whether you are creating a new database or using an existing one. Select the **Provision database throughput** option if you want to provision throughput at the database level.
    * Enter a collection ID.
-   * Enter a partition key value (for example, `/ItemID`).
+   * Enter a partition key value (for example, `ItemID`).
    * Enter a throughput that you want to provision (for example, 1000 RUs).
    * Select **OK**.
 
     :::image type="content" source="./media/how-to-provision-throughput-mongodb/provision-database-throughput-portal-mongodb-api.png" alt-text="Screenshot of Data Explorer, when creating a new collection with database level throughput":::
 
 > [!Note]
-> If you are provisioning throughput on a container in an Azure Cosmos account configured with the Azure Cosmos DB API for MongoDB, use `/myShardKey` for the partition key path.
+> If you are provisioning throughput on a container in an Azure Cosmos account configured with the Azure Cosmos DB API for MongoDB, use `myShardKey` for the partition key path.
 
 ## <a id="dotnet-mongodb"></a> .NET SDK