Merge pull request #212751 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)

Author: rmca14

articles/active-directory/fundamentals/automate-provisioning-to-applications-solutions.md

@@ -77,7 +77,7 @@ The table depicts common scenarios and the recommended technology.
 
 ## Automate provisioning users into non-Microsoft applications
 
-After identities are in Azure AD through HR-provisioning or Azure AD Connect Could Sync / Azure AD Connect Sync, the employee can use the identity to access Teams, SharePoint, and Microsoft 365 applications. However, employees still need access to many Microsoft applications to perform their work.
+After identities are in Azure AD through HR-provisioning or Azure AD Connect cloud sync / Azure AD Connect sync, the employee can use the identity to access Teams, SharePoint, and Microsoft 365 applications. However, employees still need access to many Microsoft applications to perform their work.
 
 ![Automation decision matrix](media/automate-user-provisioning-to-applications-solutions/automate-provisioning-decision-matrix.png)
 

articles/active-directory/saas-apps/olfeo-saas-provisioning-tutorial.md

@@ -47,7 +47,7 @@ The scenario outlined in this tutorial assumes that you already have the followi
 1. Login to Olfeo SAAS admin console. 
 1. Navigate to **Configuration > Annuaires**.
 1. Create a new directory and then name it.
-1. Select **Azure** provider and then click on **Cr�er** to save the new directory. 
+1. Select **Azure** provider and then click on **Créer** to save the new directory. 
 1. Navigate to the **Synchronisation** tab to see the **Tenant URL** and the **Jeton secret**. These values will be copied and pasted in the **Tenant URL** and **Secret Token** fields in the Provisioning tab of your Olfeo SAAS application in the Azure portal.
 
 ## Step 3. Add Olfeo SAAS from the Azure AD application gallery

articles/aks/use-managed-identity.md

@@ -148,7 +148,7 @@ Example:
 az role assignment create --assignee 22222222-2222-2222-2222-222222222222 --role "Contributor" --scope "/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/custom-resource-group"
 ```
 
-For user-assigned kubelet identity which is outside the default woker node resource group, you need to assign the `Managed Identity Operator`on kubelet identity.
+For user-assigned kubelet identity which is outside the default worker node resource group, you need to assign the `Managed Identity Operator`on kubelet identity.
 
 ```azurecli-interactive
 az role assignment create --assignee <control-plane-identity-principal-id> --role "Managed Identity Operator" --scope "<kubelet-identity-resource-id>"

articles/azure-monitor/autoscale/autoscale-custom-metric.md

@@ -18,6 +18,9 @@ This article describes how to set up autoscale for a web app by using a custom m
 
 Autoscale allows you to add and remove resources to handle increases and decreases in load. In this article, we'll show you how to set up autoscale for a web app by using one of the Application Insights metrics to scale the web app in and out.
 
+> [!NOTE]
+> Autoscaling on custom metrics in Application Insights is supported only for metrics published to **Standard** and **Azure.ApplicationInsights** namespaces. If any other namespaces are used for custom metrics in Application Insights, it will return **Unsupported Metric** error.
+
 Azure Monitor autoscale applies to:
 
 + [Azure Virtual Machine Scale Sets](https://azure.microsoft.com/services/virtual-machine-scale-sets/)
@@ -153,4 +156,4 @@ To learn more about autoscale, see the following articles:
 - [Overview of autoscale](./autoscale-overview.md)
 - [Azure Monitor autoscale common metrics](./autoscale-common-metrics.md)
 - [Best practices for Azure Monitor autoscale](./autoscale-best-practices.md)
-- [Autoscale REST API](/rest/api/monitor/autoscalesettings)
+- [Autoscale REST API](/rest/api/monitor/autoscalesettings)

articles/azure-monitor/logs/analyze-usage.md

@@ -171,6 +171,7 @@ If you find that you have excessive billable data for a particular data type, th
 ```kusto
 SecurityEvent 
 | summarize AggregatedValue = count() by EventID
+| order by AggregatedValue desc nulls last
 ```
 
 **Log Management** solution
@@ -179,6 +180,7 @@ SecurityEvent
 Usage 
 | where Solution == "LogManagement" and iff(isnotnull(toint(IsBillable)), IsBillable == true, IsBillable == "true") == true 
 | summarize AggregatedValue = count() by DataType
+| order by AggregatedValue desc nulls last
 ```
 
 **Perf** data type

articles/azure-resource-manager/bicep/bicep-functions-files.md

@@ -2,7 +2,7 @@
 title: Bicep functions - files
 description: Describes the functions to use in a Bicep file to load content from a file.
 ms.topic: conceptual
-ms.date: 07/08/2022
+ms.date: 09/28/2022
 ---
 
 # File functions for Bicep
@@ -21,11 +21,11 @@ Namespace: [sys](bicep-functions.md#namespaces-for-functions).
 
 | Parameter | Required | Type | Description |
 |:--- |:--- |:--- |:--- |
-| filePath | Yes | string | The path to the file to load. The path is relative to the deployed Bicep file. |
+| filePath | Yes | string | The path to the file to load. The path is relative to the deployed Bicep file, and it should be a compile-time constant (cannot use variables). |
 
 ### Remarks
 
-Use this function when you have binary content you would like to include in deployment. Rather than manually encoding the file to a base64 string and adding it to your Bicep file, load the file with this function. The file is loaded when the Bicep file is compiled to a JSON template. During deployment, the JSON template contains the contents of the file as a hard-coded string.
+Use this function when you have binary content you would like to include in deployment. Rather than manually encoding the file to a base64 string and adding it to your Bicep file, load the file with this function. The file is loaded when the Bicep file is compiled to a JSON template. Hence variables cannot be used in filePath as they are not resolved at this stage. During deployment, the JSON template contains the contents of the file as a hard-coded string.
 
 This function requires **Bicep version 0.4.412 or later**.
 
@@ -47,13 +47,13 @@ Namespace: [sys](bicep-functions.md#namespaces-for-functions).
 
 | Parameter | Required | Type | Description |
 |:--- |:--- |:--- |:--- |
-| filePath | Yes | string | The path to the file to load. The path is relative to the deployed Bicep file. |
+| filePath | Yes | string | The path to the file to load. The path is relative to the deployed Bicep file. The path is relative to the deployed Bicep file, and it should be a compile-time constant (cannot use variables). |
 | jsonPath | No | string | JSONPath expression to take only a part of the JSON into ARM. |
 | encoding | No | string | The file encoding. The default value is `utf-8`. The available options are: `iso-8859-1`, `us-ascii`, `utf-16`, `utf-16BE`, or `utf-8`.  |
 
 ### Remarks
 
-Use this function when you have JSON content or minified JSON content that is stored in a separate file. Rather than duplicating the JSON content in your Bicep file, load the content with this function. You can load a part of a JSON file by specifying a JSON path. The file is loaded when the Bicep file is compiled to the JSON template. During deployment, the JSON template contains the contents of the file as a hard-coded string.
+Use this function when you have JSON content or minified JSON content that is stored in a separate file. Rather than duplicating the JSON content in your Bicep file, load the content with this function. You can load a part of a JSON file by specifying a JSON path. The file is loaded when the Bicep file is compiled to the JSON template. Hence variables cannot be used in filePath as they are not resolved at this stage. During deployment, the JSON template contains the contents of the file as a hard-coded string.
 
 In VS Code, the properties of the loaded object are available intellisense. For example, you can create a file with values to share across many Bicep files. An example is shown in this article.
 
@@ -89,12 +89,12 @@ Namespace: [sys](bicep-functions.md#namespaces-for-functions).
 
 | Parameter | Required | Type | Description |
 |:--- |:--- |:--- |:--- |
-| filePath | Yes | string | The path to the file to load. The path is relative to the deployed Bicep file. |
+| filePath | Yes | string | The path to the file to load. The path is relative to the deployed Bicep file. The path is relative to the deployed Bicep file, and it should be a compile-time constant (cannot use variables). |
 | encoding | No | string | The file encoding. The default value is `utf-8`. The available options are: `iso-8859-1`, `us-ascii`, `utf-16`, `utf-16BE`, or `utf-8`.  |
 
 ### Remarks
 
-Use this function when you have content that is more stored in a separate file. Rather than duplicating the content in your Bicep file, load the content with this function. For example, you can load a deployment script from a file. The file is loaded when the Bicep file is compiled to the JSON template. During deployment, the JSON template contains the contents of the file as a hard-coded string.
+Use this function when you have content that is more stored in a separate file. Rather than duplicating the content in your Bicep file, load the content with this function. For example, you can load a deployment script from a file. The file is loaded when the Bicep file is compiled to the JSON template. Hence variables cannot be used in filePath as they are not resolved at this stage. During deployment, the JSON template contains the contents of the file as a hard-coded string.
 
 Use the [`loadJsonContent()`](#loadjsoncontent) function to load JSON files.
 

articles/cosmos-db/mongodb/change-log.md

@@ -41,18 +41,6 @@ The API for MongoDB now offers a built-in role-based access control (RBAC) that
 [Learn more](./how-to-setup-rbac.md)
 
 
-### Unique partial indexes in Azure Cosmos DB API for MongoDB 
-The unique partial indexes feature allows you more flexibility to specify exactly which fields in which documents you’d like to index, all while enforcing uniqueness of that field’s value. Resulting in the unique constraint being applied only to the documents that meet the specified filter expression. 
-
-[Learn more](./feature-support-42.md)
-
-
-### Azure Cosmos DB API for MongoDB unique index reindexing (Preview)
-The unique index feature for Azure Cosmos DB allows you to create unique indexes when your collection was empty and didn't contain documents. This feature provides you with more flexibility by giving you the ability to create unique indexes whenever you want to—meaning there’s no need to plan unique indexes ahead of time before inserting any data into the collection. 
-
-[Learn more](./mongodb-indexing.md) and enable the feature today by [submitting a support ticket request](https://azure.microsoft.com/support/create-ticket/)
-
-
 ### Azure Cosmos DB API for MongoDB supports version 4.2
 The Azure Cosmos DB API for MongoDB version 4.2 includes new aggregation functionality and improved security features such as client-side field encryption. These features help you accelerate development by applying the new functionality instead of developing it yourself. 
 

articles/energy-data-services/concepts-ddms.md

@@ -14,10 +14,10 @@ ms.custom: template-concept #Required; leave this attribute/value as-is.
 **Domain Data Management Service (DDMS)** – is a platform component that extends [OSDU™](https://osduforum.org) core data platform with domain specific model and optimizations. DDMS is a mechanism of a platform extension that:
 
 * delivers optimized handling of data for each (non-overlapping) "domain."
-* single vertical discipline or business area,  for example, Petrophysics, Geophysics, Seismic
-* a functional aspect of one or more vertical disciplines or business areas,  for example, Earth Model
+* pertains to a single vertical discipline or business area,  for example, Petrophysics, Geophysics, Seismic
+* serves a functional aspect of one or more vertical disciplines or business areas,  for example, Earth Model
 * delivers high performance capabilities not supported by OSDU™ generic normal APIs.
-* can help achieve the extension of OSDU™ scope to new business areas.
+* helps achieve the extension of OSDU™ scope to new business areas.
 * may be developed in a distributed manner with separate resources/sponsors.
 
 OSDU™ Technical Standard defines the following types of OSDU™ application types: