Merge pull request #218583 from MicrosoftDocs/main

11/16 Publish at 7AM

Author: huypub

articles/active-directory/verifiable-credentials/verifiable-credentials-configure-issuer.md

@@ -144,9 +144,6 @@ Now that you have a new credential, you're going to gather some information abou
 
 1. Copy your **Tenant ID**, and record it for later. The Tenant ID is the guid in the manifest URL highlighted in red above.
 
-    >[!NOTE]
-    > When setting up access policies for Azure Key Vault, you must add the access policies for both **Verifiable Credentials Service Request** and **Verifiable Credentials Service**.
-
 ## Download the sample code
 
 The sample application is available in .NET, and the code is maintained in a GitHub repository. Download the sample code from [GitHub](https://github.com/Azure-Samples/active-directory-verifiable-credentials-dotnet), or clone the repository to your local machine:

articles/active-directory/verifiable-credentials/verifiable-credentials-configure-tenant.md

@@ -137,7 +137,7 @@ To add the required permissions, follow these steps:
 
 1. Select **APIs my organization uses**.
 
-1. Search for the **Verifiable Credentials Service Request** and **Verifiable Credentials Service** service principals, and select them.
+1. Search for the **Verifiable Credentials Service Request** service principal and select it.
 
     :::image type="content" source="media/verifiable-credentials-configure-tenant/add-app-api-permissions-select-service-principal.png" alt-text="Screenshot that shows how to select the service principal.":::
 
@@ -159,14 +159,15 @@ You can choose to grant issuance and presentation permissions separately if you
 1. Navigate to the Verified ID service in the Azure portal.  
 1. Select **Registration**.
 1. Notice that there are two sections:
-    1. Website ID registration
-    1. Domain verification.
+    1. DID registration
+    1. Domain ownership verification.
 1. Select on each section and download the JSON file under each.
 1. Create a website that you can use to distribute the files. If you specified **https://contoso.com** as your domain, the URLs for each of the files would look as shown below:
     - `https://contoso.com/.well-known/did.json`
     - `https://contoso.com/.well-known/did-configuration.json`
 
 Once that you have successfully completed the verification steps, you are ready to continue to the next tutorial.
+If you have selected ION as the trust system, you will not see the DID registration section as it is not applicable for ION and you only have to distribute the did-configuration.json file. 
 
 ## Next steps
 

articles/aks/learn/tutorial-kubernetes-workload-identity.md

@@ -3,7 +3,7 @@ title: Tutorial - Use a workload identity with an application on Azure Kubernete
 description: In this Azure Kubernetes Service (AKS) tutorial, you deploy an Azure Kubernetes Service cluster and configure an application to use a workload identity.
 services: container-service
 ms.topic: tutorial
-ms.date: 09/29/2022
+ms.date: 11/16/2022
 ---
 
 # Tutorial: Use a workload identity with an application on Azure Kubernetes Service (AKS)
@@ -223,8 +223,8 @@ spec:
     - image: ghcr.io/azure/azure-workload-identity/msal-go
       name: oidc
       env:
-      - name: KEYVAULT_NAME
-        value: ${KEYVAULT_NAME}
+      - name: KEYVAULT_URL
+        value: ${KEYVAULT_URL}
       - name: SECRET_NAME
         value: ${KEYVAULT_SECRET_NAME}
   nodeSelector:
@@ -302,4 +302,4 @@ This tutorial is for introductory purposes. For guidance on a creating full solu
 [az-aks-get-credentials]: /cli/azure/aks#az-aks-get-credentials
 [az-identity-federated-credential-create]: /cli/azure/identity/federated-credential#az-identity-federated-credential-create
 [aks-tutorial]: ../tutorial-kubernetes-prepare-app.md
-[aks-solution-guidance]: /azure/architecture/reference-architectures/containers/aks-start-here
+[aks-solution-guidance]: /azure/architecture/reference-architectures/containers/aks-start-here

articles/azure-maps/how-to-dev-guide-js-sdk.md

@@ -30,6 +30,16 @@ The Azure Maps JavaScript/TypeScript REST SDK (JavaScript SDK) supports searchin
 > az maps account create --kind "Gen2" --account-name "myMapAccountName" --resource-group "<resource group>" --sku "G2"
 > ```
 
+## Create a Node.js project
+
+The example below creates a new directory then a Node.js program named _mapsDemo_ using npm:
+
+```powershell
+mkdir mapsDemo
+cd mapsDemo
+npm init
+```
+
 ## Install the search package
 
 To use Azure Maps JavaScript SDK, you'll need to install the search package. Each of the Azure Maps services including search, routing, rendering and geolocation are each in their own package.
@@ -55,16 +65,6 @@ mapsDemo
 | [Search][search readme] | [@azure/maps-search][search package] | [search samples][search sample] |
 | [Route][js route readme] | [@azure-rest/maps-route][js route package] | [route samples][js route sample] |
 
-## Create a Node.js project
-
-The example below creates a new directory then a Node.js program named _mapsDemo_ using npm:
-
-```powershell
-mkdir mapsDemo
-cd mapsDemo
-npm init
-```
-
 ## Create and authenticate a MapsSearchClient
 
 You'll need a `credential` object for authentication when creating the `MapsSearchClient` object used to access the Azure Maps search APIs. You can use either an Azure Active Directory (Azure AD) credential or an Azure subscription key to authenticate. For more information on authentication, see [Authentication with Azure Maps][authentication].

articles/azure-monitor/autoscale/autoscale-common-scale-patterns.md

@@ -1,59 +1,78 @@
 ---
 title: Overview of common autoscale patterns
 description: Learn some of the common patterns to auto scale your resource in Azure.
+author: EdB-MSFT
 ms.topic: conceptual
-ms.date: 04/22/2022
+ms.date: 11/17/2022
 ms.subservice: autoscale
-ms.reviewer: riroloff
+ms.author: edbaynash
+ms.reviewer: akkumari
 ---
 # Overview of common autoscale patterns
-This article describes some of the common patterns to scale your resource in Azure.
 
-Azure Monitor autoscale applies only to [Virtual Machine Scale Sets](https://azure.microsoft.com/services/virtual-machine-scale-sets/), [Cloud Services](https://azure.microsoft.com/services/cloud-services/), [App Service - Web Apps](https://azure.microsoft.com/services/app-service/web/), and [API Management services](../../api-management/api-management-key-concepts.md).
+Autoscale settings help ensure that you have the right amount of resources running to handle the fluctuating load of your application. You can configure autoscale settings to be triggered based on metrics that indicate load or performance, or triggered at a scheduled date and time. 
 
-## Lets get started
+Azure autoscale supports many resource types. For more information about supported resources, see [autoscale supported resources](./autoscale-overview.md#supported-services-for-autoscale).
 
-This article assumes that you are familiar with auto scale. You can [get started here to scale your resource][1]. The following are some of the common scale patterns.
+This article describes some of the common patterns you can use to scale your resources in Azure.
+## Prerequisites
 
-## Scale based on CPU
+This article assumes that you're familiar with auto scale. [Get started here to scale your resource](./autoscale-get-started.md). 
 
-You have a web app (/VMSS/cloud service role) and
+## Scale based on metrics
 
-- You want to scale out/scale in based on CPU.
-- Additionally, you want to ensure there is a minimum number of instances.
-- Also, you want to ensure that you set a maximum limit to the number of instances you can scale to.
+Scale your resource based on metrics produce by the resource itself or any other resource.
+For example:
+* Scale your Virtual Machine Scale Set based on the CPU usage of the virtual machine.
+* Ensure a minimum number of instances.
+* Set a maximum limit on the number of instances.  
 
-[![Scale based on CPU](./media/autoscale-common-scale-patterns/scale-based-on-cpu.png)](./media/autoscale-common-scale-patterns/scale-based-on-cpu.png#lightbox)
+The image below shows a default scale condition for a Virtual Machine Scale Set
+ * The **Scale rule** tab shows that the metric source is the scale set itself and the metric used is Percentage CPU.
+ * The minimum number of instances running is set to 2.
+ * The maximum number of instances is set to 10.
+ * When the scale set starts, the default number of instances is 3.
 
-## Scale differently on weekdays vs weekends
+:::image type="content" source="./media/autoscale-common-scale-patterns/scale-based-on-cpu.png" alt-text="A screenshot showing an autoscale setting, scaling by CPU %." lightbox="./media/autoscale-common-scale-patterns/scale-based-on-cpu.png":::
 
-You have a web app (/VMSS/cloud service role) and
+## Scale based on another resource's metric
 
-- You want 3 instances by default (on weekdays)
-- You don't expect traffic on weekends and hence you want to scale down to 1 instance on weekends.
+Scale a resource based on the metrics from a different resource.  
+The image below shows a scale rule that is scaling a Virtual Machine Scale Set based on the number of allocated ports on a load balancer.  
 
-[![Scale differently on weekdays vs weekends](./media/autoscale-common-scale-patterns/scale-differently-on-weekends.png)](./media/autoscale-common-scale-patterns/scale-differently-on-weekends.png#lightbox)
+:::image type="content" source="./media/autoscale-common-scale-patterns/scale-rule-other-resource.png" alt-text="A screenshot showing autoscale rule based on load balancer metrics." lightbox="./media/autoscale-common-scale-patterns/scale-rule-other-resource.png":::
 
-## Scale differently during holidays
+## Scale differently on weekends
 
-You have a web app (/VMSS/cloud service role) and
+You can scale your resources differently on different days of the week..  
+For example, you have a web app and want to:
+- Set a minimum of 3 instances on weekdays.
+- Scale down to 1 instance on weekends when there's less traffic.
 
-- You want to scale up/down based on CPU usage by default
-- However, during holiday season (or specific days that are important for your business) you want to override the defaults and have more capacity at your disposal.
+:::image type="content" source="./media/autoscale-common-scale-patterns/scale-differently-on-weekends.png" alt-text="A screenshot showing two autoscale profiles, one default and one for weekends." lightbox="./media/autoscale-common-scale-patterns/scale-differently-on-weekends.png":::
 
-[![Scale differently on holidays](./media/autoscale-common-scale-patterns/scale-for-holiday.png)](./media/autoscale-common-scale-patterns/scale-for-holiday.png#lightbox)
+## Scale differently during specific events
 
-## Scale based on custom metric
+You can set your scale rules and instance limits differently for specific events.  
+For example: 
+- Set a minimum of 3 instances by default
+- For the week of Back Friday, set the minimum number of instances to 10 to handle the anticipated traffic.
 
-You have a web front end and an API tier that communicates with the backend.
+:::image type="content" source="./media/autoscale-common-scale-patterns/scale-for-event.png" alt-text="A screenshot showing two autoscale profiles, one default and one for a specific date range." lightbox="./media/autoscale-common-scale-patterns/scale-for-event.png":::
 
-- You want to scale the API tier based on custom events in the front end (example: You want to scale your checkout process based on the number of items in the shopping cart)
+## Scale based on custom metrics
+Scale by custom metrics generated by your application.  
+For example, you have a web front end and an API tier that communicates with the backend, and you want to scale the API tier based on custom events in the front end.
 
-![Scale based on custom metric][5]
+:::image type="content" source="./media/autoscale-common-scale-patterns/custom-metric-scale.png" alt-text="A screenshot showing an autoscale profile, and rule scaling by a custom metric." lightbox="./media/autoscale-common-scale-patterns/custom-metric-scale.png":::
 
-<!--Reference-->
-[1]: ./autoscale-get-started.md
-[2]: ./media/autoscale-common-scale-patterns/scale-based-on-cpu.png
-[3]: ./media/autoscale-common-scale-patterns/weekday-weekend-scale.png
-[4]: ./media/autoscale-common-scale-patterns/holidays-scale.png
-[5]: ./media/autoscale-common-scale-patterns/custom-metric-scale.png
+Next steps
+
+Learn more about autoscale by referring to the following articles :
+
+* [Azure Monitor autoscale common metrics](./autoscale-common-metrics.md)
+* [Azure Monitor autoscale custom metrics](./autoscale-custom-metric.md)
+* [Autoscale with multiple profiles](./autoscale-multiprofile.md)
+* [Flapping in Autoscale](./autoscale-custom-metric.md)
+* [Use autoscale actions to send email and webhook alert notifications](./autoscale-webhook-email.md)
+* [Autoscale REST API](/rest/api/monitor/autoscalesettings)