Merge pull request #192083 from MicrosoftDocs/main

3/17 PM Publish

Author: huypub

.openpublishing.redirection.active-directory.json

@@ -52,7 +52,7 @@ More information about the location condition in Conditional Access can be found
    1. Under **Include**, select **Selected locations**
    1. Select the blocked location you created for your organization.
    1. Click **Select**.
-1. Under **Access controls** > select **Block Access**, and select **Select**.
+1. Under **Access controls** > select **Block Access**, and click **Select**.
 1. Confirm your settings and set **Enable policy** to **Report-only**.
 1. Select **Create** to create to enable your policy.
 

articles/active-directory/conditional-access/howto-conditional-access-policy-location.md

@@ -104,8 +104,6 @@
 - name: Reference
   expanded: true
   items:
-  - name: Azure Active Directory SLA performance
-    href: reference-azure-ad-sla-performance.md
   - name: Basic info in the sign-in logs
     href: reference-basic-info-sign-in-logs.md
   - name: Azure AD PowerShell cmdlets for reporting

articles/active-directory/reports-monitoring/reference-azure-ad-sla-performance.md

@@ -9,7 +9,7 @@ ms.service: active-directory
 ms.topic: how-to
 ms.subservice: roles
 ms.workload: identity
-ms.date: 08/06/2021
+ms.date: 03/17/2022
 ms.author: rolyon
 ms.reviewer: anandy
 ms.custom: oldportal;it-pro;
@@ -30,7 +30,7 @@ To use PowerShell commands to do the following:
 
 You must have the following module installed:
 
-- [AzureAD](https://www.powershellgallery.com/packages/AzureAD) version 2.0.2.137 or later
+- [AzureAD](https://www.powershellgallery.com/packages/AzureAD) (current version)
 
 
 #### Check AzureAD version
@@ -46,7 +46,7 @@ You should see output similar to the following:
 ```powershell
 Version    Name                                Repository           Description
 -------    ----                                ----------           -----------
-2.0.2.137  AzureAD                             PSGallery            Azure Active Directory V2 General Availability M...
+2.0.2.140  AzureAD                             PSGallery            Azure Active Directory V2 General Availability M...
 ```
 
 #### Install AzureAD
@@ -92,7 +92,7 @@ To use AzureAD, follow these steps to make sure it is imported into the current
     ```powershell
     ModuleType Version    Name                                ExportedCommands
     ---------- -------    ----                                ----------------
-    Binary     2.0.2.137  AzureAD                             {Add-AzureADApplicationOwner, Add-AzureADDeviceRegisteredO...
+    Binary     2.0.2.140  AzureAD                             {Add-AzureADApplicationOwner, Add-AzureADDeviceRegisteredO...
     ```
 
 ## AzureADPreview module
@@ -106,7 +106,7 @@ To use PowerShell commands to do the following:
 
 You must have the following module installed:
 
-- [AzureADPreview](https://www.powershellgallery.com/packages/AzureADPreview) version 2.0.2.138 or later
+- [AzureADPreview](https://www.powershellgallery.com/packages/AzureADPreview) (current version)
 
 
 #### Check AzureADPreview version
@@ -122,7 +122,7 @@ You should see output similar to the following:
 ```powershell
 Version    Name                                Repository           Description
 -------    ----                                ----------           -----------
-2.0.2.138  AzureADPreview                      PSGallery            Azure Active Directory V2 Preview Module. ...
+2.0.2.149  AzureADPreview                      PSGallery            Azure Active Directory V2 Preview Module. ...
 ```
 
 #### Install AzureADPreview
@@ -168,7 +168,7 @@ To use AzureADPreview, follow these steps to make sure it is imported into the c
     ```powershell
     ModuleType Version    Name                                ExportedCommands
     ---------- -------    ----                                ----------------
-    Binary     2.0.2.138  AzureADPreview                      {Add-AzureADAdministrativeUnitMember, Add-AzureADApplicati...
+    Binary     2.0.2.149  AzureADPreview                      {Add-AzureADAdministrativeUnitMember, Add-AzureADApplicati...
     ```
 
 ## Graph Explorer

articles/active-directory/reports-monitoring/toc.yml

@@ -900,7 +900,7 @@ This example shows how to return a 401 response if the authorization token is in
 
 This policy can be used in the following policy [sections](./api-management-howto-policies.md#sections) and [scopes](./api-management-howto-policies.md#scopes).
 
--   **Policy sections:** outbound, backend, on-error
+-   **Policy sections:** inbound, outbound, backend, on-error
 -   **Policy scopes:** all scopes
 
 ## <a name="set-variable"></a> Set variable

articles/active-directory/roles/prerequisites.md

@@ -5,12 +5,17 @@ author: madsd
 
 ms.assetid: 4cc82439-8791-48a4-9485-de6d8e1d1a08
 ms.topic: article
-ms.date: 01/11/2017
+ms.date: 03/15/2022
 ms.author: madsd
 ms.custom: seodec18
 
 ---
 # How To Control Inbound Traffic to an App Service Environment
+
+> [!IMPORTANT]
+> This article is about App Service Environment v1. App Service Environment v1 will be retired on 31 August 2024. There's a new version of App Service Environment that is easier to use and runs on more powerful infrastructure. To learn more about the new version, start with the [Introduction to the App Service Environment](overview.md). If you're currently using App Service Environment v1, please follow the steps in [this article](migration-alternatives.md) to migrate to the new version.
+>
+
 ## Overview
 An App Service Environment can be created in **either** an Azure Resource Manager virtual network, **or** a classic deployment model [virtual network][virtualnetwork].  A new virtual network and new subnet can be defined at the time an App Service Environment is created. Instead, an App Service Environment can be created in a pre-existing virtual network and pre-existing subnet.  As of June 2016, ASEs can also be deployed into virtual networks that use either public address ranges or RFC1918 address spaces (private addresses).  For more information, see [How to Create an ASEv1 from template](app-service-app-service-environment-create-ilb-ase-resourcemanager.md).
 

articles/api-management/api-management-advanced-policies.md

@@ -5,15 +5,15 @@ author: madsd
 
 ms.assetid: 091decb6-b0de-42a1-9f2f-c18d9b2e67df
 ms.topic: article
-ms.date: 10/10/2021
+ms.date: 03/15/2022
 ms.author: madsd
 ms.custom: seodec18
 
 ---
 # How To Create an ILB ASEv1 Using Azure Resource Manager Templates
 
-> [!NOTE] 
-> This article is about the App Service Environment v1. There is a newer version of the App Service Environment that is easier to use and runs on more powerful infrastructure. To learn more about the new version start with the [Introduction to the App Service Environment](intro.md).
+> [!IMPORTANT]
+> This article is about App Service Environment v1. App Service Environment v1 will be retired on 31 August 2024. There's a new version of App Service Environment that is easier to use and runs on more powerful infrastructure. To learn more about the new version, start with the [Introduction to the App Service Environment](overview.md). If you're currently using App Service Environment v1, please follow the steps in [this article](migration-alternatives.md) to migrate to the new version.
 >
 
 ## Overview

articles/app-service/environment/app-service-app-service-environment-control-inbound-traffic.md

@@ -5,15 +5,16 @@ author: madsd
 
 ms.assetid: 78e6d4f5-da46-4eb5-a632-b5fdc17d2394
 ms.topic: article
-ms.date: 07/11/2017
+ms.date: 03/15/2022
 ms.author: madsd
 ms.custom: seodec18
 
 ---
 # Introduction to App Service Environment v1
 
-> [!NOTE]
-> This article is about the App Service Environment v1. There is a newer version of the App Service Environment that is easier to use and runs on more powerful infrastructure. To learn more about the new version start with the [Introduction to the App Service Environment](overview.md).
+> [!IMPORTANT]
+> This article is about App Service Environment v1. App Service Environment v1 will be retired on 31 August 2024. There's a new version of App Service Environment that is easier to use and runs on more powerful infrastructure. To learn more about the new version, start with the [Introduction to the App Service Environment](overview.md). If you're currently using App Service Environment v1, please follow the steps in [this article](migration-alternatives.md) to migrate to the new version.
+>
 
 ## Overview
 

articles/app-service/environment/app-service-app-service-environment-create-ilb-ase-resourcemanager.md

@@ -5,12 +5,17 @@ author: madsd
 
 ms.assetid: 73ce0213-bd3e-4876-b1ed-5ecad4ad5601
 ms.topic: article
-ms.date: 08/30/2016
+ms.date: 03/15/2022
 ms.author: madsd
 ms.custom: seodec18
 
 ---
 # Implementing a Layered Security Architecture with App Service Environments
+
+> [!IMPORTANT]
+> This article is about App Service Environment v1. App Service Environment v1 will be retired on 31 August 2024. There's a new version of App Service Environment that is easier to use and runs on more powerful infrastructure. To learn more about the new version, start with the [Introduction to the App Service Environment](overview.md). If you're currently using App Service Environment v1, please follow the steps in [this article](migration-alternatives.md) to migrate to the new version.
+>
+
 Since App Service Environments provide an isolated runtime environment deployed into a virtual network, developers can create a layered security architecture providing differing levels of network access for each physical application tier.
 
 A common desire is to hide API back-ends from general Internet access, and only allow APIs to be called by upstream web apps.  [Network security groups (NSGs)][NetworkSecurityGroups] can be used on subnets containing App Service Environments to restrict public access to API applications.