Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into alerts-articles

Author: paulth1

.openpublishing.redirection.json

@@ -34262,6 +34262,11 @@
   "source_path_from_root": "/articles/virtual-machines/linux/copy-files-to-linux-vm-using-scp.md",
   "redirect_url": "/azure/virtual-machines/copy-files-to-vm-using-scp",
   "redirect_document_id": false
+},
+{
+  "source_path_from_root": "/articles/web-application-firewall/afds/waf-front-door-rate-limit-powershell.md",
+  "redirect_url": "/azure/web-application-firewall/afds/waf-front-door-rate-limit-configure",
+  "redirect_document_id": true
 }
 	]
 }

articles/active-directory/manage-apps/configure-user-consent.md

@@ -2,14 +2,15 @@
 title: Configure how users consent to applications
 description: Learn how to manage how and when users can consent to applications that will have access to your organization's data.
 services: active-directory
-author: psignoret
+author: yuhko-msft
 manager: CelesteDG
 ms.service: active-directory
 ms.subservice: app-mgmt
 ms.workload: identity
 ms.topic: how-to
 ms.date: 08/10/2022
-ms.author: phsignor
+ms.author: yuhko
+ms.reviewer: phsignor
 ms.custom: contperf-fy21q2, contperf-fy22q2
 
 #customer intent: As an admin, I want to configure how end-users consent to applications.

articles/active-directory/manage-apps/manage-app-consent-policies.md

@@ -2,13 +2,14 @@
 title: Manage app consent policies
 description: Learn how to manage built-in and custom app consent policies to control when consent can be granted.
 services: active-directory
-author: psignoret
+author: yuhko-msft
 ms.service: active-directory
 ms.subservice: app-mgmt
 ms.workload: identity
 ms.topic: how-to
 ms.date: 09/02/2021
-ms.author: phsignor
+ms.author: yuhko
+ms.reviewer: phsignor
 ms.custom: contperf-fy21q2
 
 #customer intent: As an admin, I want to manage app consent policies for enterprise applications in Azure AD

articles/active-directory/managed-identities-azure-resources/qs-configure-template-windows-vm.md

@@ -120,7 +120,7 @@ In this section, you assign a user-assigned managed identity to an Azure VM usin
 
 ### Assign a user-assigned managed identity to an Azure VM
 
-To assign a user-assigned identity to a VM, your account needs the [Virtual Machine Contributor](../../role-based-access-control/built-in-roles.md#virtual-machine-contributor) and [Managed Identity Operator](../../role-based-access-control/built-in-roles.md#managed-identity-operator) role assignments. No other Azure AD directory role assignments are required.
+To assign a user-assigned identity to a VM, your account needs the [Managed Identity Operator](../../role-based-access-control/built-in-roles.md#managed-identity-operator) role assignment. No other Azure AD directory role assignments are required.
 
 1. Under the `resources` element, add the following entry to assign a user-assigned managed identity to your VM.  Be sure to replace `<USERASSIGNEDIDENTITY>` with the name of the user-assigned managed identity you created.
 

articles/active-directory/saas-apps/fortigate-ssl-vpn-tutorial.md

@@ -9,7 +9,7 @@ ms.service: active-directory
 ms.subservice: saas-app-tutorial
 ms.workload: identity
 ms.topic: tutorial
-ms.date: 05/13/2022
+ms.date: 09/08/2022
 ms.author: jeedes
 ---
 
@@ -219,7 +219,7 @@ To complete these steps, you'll need the values you recorded earlier:
     		set entity-id < Identifier (Entity ID)Entity ID>
     		set single-sign-on-url < Reply URL Reply URL>
     		set single-logout-url <Logout URL>
-    		set idp-entity-id <Azure AD Identifier>
+    		set idp-entity-id <Azure Login URL>
 		set idp-single-sign-on-url <Azure AD Identifier>
     		set idp-single-logout-url <Azure Logout URL>
     		set idp-cert <Base64 SAML Certificate Name>

articles/active-directory/saas-apps/infrascale-cloud-backup-tutorial.md

@@ -9,7 +9,7 @@ ms.service: active-directory
 ms.subservice: saas-app-tutorial
 ms.workload: identity
 ms.topic: tutorial
-ms.date: 06/24/2022
+ms.date: 09/08/2022
 ms.author: jeedes
 
 ---
@@ -78,28 +78,11 @@ Follow these steps to enable Azure AD SSO in the Azure portal.
     b. In the **Reply URL** textbox, type the URL:
     `https://dashboard.managedoffsitebackup.net/Account/AssertionConsumerService`  
 
-    c. In the **Sign-on URL** text box, type one of the following URLs:
-    
-    | **Sign-on URL** |
-    |------------|
-    | `https://dashboard.avgonlinebackup.com/Account/SingleSignOn` |
-    | `https://dashboard.infrascale.com/Account/SingleSignOn` |
-    | `https://dashboard.managedoffsitebackup.net/Account/SingleSignOn` |
-    | `https://dashboard.sosonlinebackup.com/Account/SingleSignOn` |
-    |`https://dashboard.trustboxbackup.com/Account/SingleSignOn` |
-    | `https://radialpoint-dashboard.managedoffsitebackup.net/Account/SingleSignOn` |
-    | `https://dashboard-cw.infrascale.com/Account/SingleSignOn` |
-    | `https://dashboard.digicelcloudbackup.com/Account/SingleSignOn` |
-    | `https://dashboard-cw.sosonlinebackup.com/Account/SingleSignOn` |
-    |`https://dashboard.my-data.dk/Account/SingleSignOn` |
-    |`https://dashboard.beesafe.nu/Account/SingleSignOn` |
-    |`https://dashboard.bekcloud.com/Account/SingleSignOn` |
-    | `https://dashboard.alltimesecure.com/Account/SingleSignOn` |
-    | `https://dashboard-ec1.sosonlinebackup.com/Account/SingleSignOn` |
-    | `https://dashboard.glcsecurecloud.com/Account/SingleSignOninfrascalecloudbackup.com/infrascalecloudbackup.com/` |
+    c. The **Sign-on URL** text box requires a specific URL for your company. The general pattern of the URL is:
+    `https://[OptionalPrefix]dashboard[OptionalSuffix].CompanySpecificString.[com/net,etc]/Account/SingleSignOn`
 
     > [!Note]
-    > The Identifier value is not real. Update this value with the actual Identifier URL. Contact [Infrascale Cloud Backup support team](mailto:[email protected]) to get the value. You can also refer to the patterns shown in the **Basic SAML Configuration** section in the Azure portal.
+    > Do not enter this in the Sign-on URL text box. The Identifier value is not a real URL – just a general pattern. Update this value with the actual Identifier URL obtained from Infrascale. Contact [Infrascale Cloud Backup support team](mailto:[email protected]) to get the value.
 
 1. On the **Set up single sign-on with SAML** page, In the **SAML Signing Certificate** section, click copy button to copy **App Federation Metadata Url** and save it on your computer.
 

articles/active-directory/verifiable-credentials/decentralized-identifier-overview.md

@@ -19,7 +19,7 @@ ms.reviewer:
 
 Our digital and physical lives are increasingly linked to the apps, services, and devices we use to access a rich set of experiences. This digital transformation allows us to interact with hundreds of companies and thousands of other users in ways that were previously unimaginable.
 
-But identity data has too often been exposed in security breaches. These breaches affect our social, professional, and financial lives. Microsoft believes that there’s a better way. Every person has a right to an identity that they own and control, one that securely stores elements of their digital identity and preserves privacy. This primer explains how we are joining hands with a diverse community to build an open, trustworthy, interoperable, and standards-based Decentralized Identity (DID) solution for individuals and organizations.
+But identity data has too often been exposed in security breaches. These breaches affect our social, professional, and financial lives. Microsoft believes that there’s a better way. Every person has a right to an identity that they own and control, one that securely stores elements of their digital identity and preserves privacy. This primer explains how we are joining hands with a diverse community to build an open, trustworthy, interoperable, and standards-based Decentralized Identity solution for individuals and organizations.
 
 ## Why we need Decentralized Identity
 

articles/aks/TOC.yml

@@ -44,7 +44,7 @@
           href: quickstart-helm.md
         - name: Develop with Dapr
           href: quickstart-dapr.md
-    - name: Subscribe to AKS events with Event Grid (Preview)
+    - name: Subscribe to AKS events with Event Grid
       href: quickstart-event-grid.md
 - name: Tutorials
   items:

articles/aks/quickstart-event-grid.md

@@ -1,5 +1,5 @@
 ---
-title: Subscribe to Azure Kubernetes Service events with Azure Event Grid  (Preview)
+title: Subscribe to Azure Kubernetes Service events with Azure Event Grid
 description: Use Azure Event Grid to subscribe to Azure Kubernetes Service events
 services: container-service
 author: zr-msft
@@ -8,70 +8,17 @@ ms.date: 07/12/2021
 ms.author: zarhoads
 ---
 
-# Quickstart: Subscribe to Azure Kubernetes Service (AKS) events with Azure Event Grid (Preview)
+# Quickstart: Subscribe to Azure Kubernetes Service (AKS) events with Azure Event Grid
 
 Azure Event Grid is a fully managed event routing service that provides uniform event consumption using a publish-subscribe model.
 
 In this quickstart, you'll create an AKS cluster and subscribe to AKS events.
 
-[!INCLUDE [preview features callout](./includes/preview/preview-callout.md)]
-
 ## Prerequisites
 
 * An Azure subscription. If you don't have an Azure subscription, you can create a [free account](https://azure.microsoft.com/free).
 * [Azure CLI][azure-cli-install] or [Azure PowerShell][azure-powershell-install] installed.
 
-### Register the `EventgridPreview` preview feature
-
-To use the feature, you must also enable the `EventgridPreview` feature flag on your subscription.
-
-### [Azure CLI](#tab/azure-cli)
-
-Register the `EventgridPreview` feature flag by using the [az feature register][az-feature-register] command, as shown in the following example:
-
-```azurecli-interactive
-az feature register --namespace "Microsoft.ContainerService" --name "EventgridPreview"
-```
-
-It takes a few minutes for the status to show *Registered*. Verify the registration status by using the [az feature list][az-feature-list] command:
-
-```azurecli-interactive
-az feature list -o table --query "[?contains(name, 'Microsoft.ContainerService/EventgridPreview')].{Name:name,State:properties.state}"
-```
-
-When ready, refresh the registration of the *Microsoft.ContainerService* resource provider by using the [az provider register][az-provider-register] command:
-
-```azurecli-interactive
-az provider register --namespace Microsoft.ContainerService
-```
-
-[!INCLUDE [event-grid-register-provider-cli.md](../../includes/event-grid-register-provider-cli.md)]
-
-### [Azure PowerShell](#tab/azure-powershell)
-
-Register the `EventgridPreview` feature flag by using the [Register-AzProviderPreviewFeature][register-azproviderpreviewfeature] cmdlet, as shown in the following example:
-
-```azurepowershell-interactive
-Register-AzProviderPreviewFeature -ProviderNamespace Microsoft.ContainerService -Name EventgridPreview
-```
-
-It takes a few minutes for the status to show *Registered*. Verify the registration status by using the [Get-AzProviderPreviewFeature][get-azproviderpreviewfeature] cmdlet:
-
-```azurepowershell-interactive
-Get-AzProviderPreviewFeature -ProviderNamespace Microsoft.ContainerService -Name EventgridPreview |
- Format-Table -Property Name, @{name='State'; expression={$_.Properties.State}}
-```
-
-When ready, refresh the registration of the *Microsoft.ContainerService* resource provider by using the [Register-AzResourceProvider][register-azresourceprovider] command:
-
-```azurepowershell-interactive
-Register-AzResourceProvider -ProviderNamespace Microsoft.ContainerService
-```
-
-[!INCLUDE [event-grid-register-provider-powershell.md](../../includes/event-grid-register-provider-powershell.md)]
-
----
-
 ## Create an AKS cluster
 
 ### [Azure CLI](#tab/azure-cli)
@@ -267,12 +214,6 @@ To learn more about AKS, and walk through a complete code to deployment example,
 [new-azeventhub]: /powershell/module/az.eventhub/new-azeventhub
 [az-eventgrid-event-subscription-create]: /cli/azure/eventgrid/event-subscription#az-eventgrid-event-subscription-create
 [new-azeventgridsubscription]: /powershell/module/az.eventgrid/new-azeventgridsubscription
-[az-feature-register]: /cli/azure/feature#az_feature_register
-[register-azproviderpreviewfeature]: /powershell/module/az.resources/register-azproviderpreviewfeature
-[az-feature-list]: /cli/azure/feature#az_feature_list
-[get-azproviderpreviewfeature]: /powershell/module/az.resources/get-azproviderpreviewfeature
-[az-provider-register]: /cli/azure/provider#az_provider_register
-[register-azresourceprovider]: /powershell/module/az.resources/register-azresourceprovider
 [az-group-delete]: /cli/azure/group#az_group_delete
 [sp-delete]: kubernetes-service-principal.md#other-considerations
 [remove-azresourcegroup]: /powershell/module/az.resources/remove-azresourcegroup

articles/api-management/api-management-howto-mutual-certificates-for-clients.md

@@ -45,7 +45,8 @@ For more information, see [API Management access restriction policies](api-manag
 You can also create policy expressions with the [`context` variable](api-management-policy-expressions.md#ContextVariables) to check client certificates. Examples in the following sections show expressions using the `context.Request.Certificate` property and other `context` properties.
 
 > [!IMPORTANT]
-> Starting May 2021, the `context.Request.Certificate` property only requests the certificate when the API Management instance's [`hostnameConfiguration`](/rest/api/apimanagement/current-ga/api-management-service/create-or-update#hostnameconfiguration) sets the `negotiateClientCertificate` property to True. By default, `negotiateClientCertificate` is set to False.
+> * Starting May 2021, the `context.Request.Certificate` property only requests the certificate when the API Management instance's [`hostnameConfiguration`](/rest/api/apimanagement/current-ga/api-management-service/create-or-update#hostnameconfiguration) sets the `negotiateClientCertificate` property to True. By default, `negotiateClientCertificate` is set to False.
+> * If TLS renegotiation is disabled in your client, you may see TLS errors when requesting the certificate using the `context.Request.Certificate` property. If this occurs, enable TLS renegotation settings in the client. 
 
 ### Checking the issuer and subject