Refresh of azps docs (MicrosoftDocs#1919)

Author: mikefrobbins

docs-conceptual/azps-5.9.0/authenticate-azureps.md

@@ -3,7 +3,7 @@ title: Sign in with Azure PowerShell
 description: How to sign in with Azure PowerShell as a user, service principal, or with managed identities for Azure resources.
 ms.devlang: powershell
 ms.topic: conceptual
-ms.date: 08/10/2021
+ms.date: 09/27/2021
 ms.custom: devx-track-azurepowershell
 ms.service: azure-powershell
 ---
@@ -52,7 +52,7 @@ in a variable to be used in the next two sections of this article.
 $tenantId = (Get-AzContext).Tenant.Id
 ```
 
-## Sign in with a service principal <a name="sp-signin"/>
+## Sign in with a service principal
 
 Service principals are non-interactive Azure accounts. Like other user accounts, their permissions
 are managed with Azure Active Directory. By granting a service principal only the permissions it
@@ -61,11 +61,10 @@ needs, your automation scripts stay secure.
 To learn how to create a service principal for use with Azure PowerShell, see
 [Create an Azure service principal with Azure PowerShell](create-azure-service-principal-azureps.md).
 
-To sign in with a service principal, use the `-ServicePrincipal` argument with the
-`Connect-AzAccount` cmdlet. You'll also need the service principal's application ID, sign-in
-credentials, and the tenant ID associate with the service principal. How you sign in with a service
-principal depends on whether it's configured for password-based or certificate-based
-authentication.
+To sign in with a service principal, use the `ServicePrincipal` parameter of the `Connect-AzAccount`
+cmdlet. You'll also need the service principal's application ID, sign-in credentials, and the tenant
+ID associate with the service principal. How you sign in with a service principal depends on whether
+it's configured for password-based or certificate-based authentication.
 
 ### Password-based authentication
 
@@ -109,17 +108,18 @@ local certificate store based on a certificate thumbprint.
 Connect-AzAccount -ApplicationId $appId -Tenant $tenantId -CertificateThumbprint <thumbprint>
 ```
 
-When using a service principal instead of a registered application, add the `-ServicePrincipal` argument
-and provide the service principal's Application ID as the `-ApplicationId` parameter's value.
+When using a service principal instead of a registered application, specify the `ServicePrincipal`
+parameter and provide the service principal's Application ID as the `-ApplicationId` parameter's
+value.
 
 ```azurepowershell-interactive
 Connect-AzAccount -ServicePrincipal -ApplicationId $servicePrincipalId -Tenant $tenantId -CertificateThumbprint <thumbprint>
 ```
 
 In PowerShell 5.1, the certificate store can be managed and inspected with the
-[PKI](/powershell/module/pki) module. For PowerShell Core 6.x and later, the process is more
-complicated. The following scripts show you how to import an existing certificate into the
-certificate store accessible by PowerShell.
+[PKI](/powershell/module/pki) module. For PowerShell 6.x and later, the process is more complicated.
+The following scripts show you how to import an existing certificate into the certificate store
+accessible by PowerShell.
 
 #### Import a certificate in PowerShell 5.1
 
@@ -162,23 +162,23 @@ that assigned identity.
 
 ## Sign in with a non-default tenant or as a Cloud Solution Provider (CSP)
 
-If your account is associated with more than one tenant, sign-in requires the `-Tenant` parameter to
+If your account is associated with more than one tenant, sign-in requires the `Tenant` parameter to
 be specified when connecting. This parameter works with any sign-in method. When logging in, this
 parameter value can either be the Azure object ID of the tenant (Tenant ID) or the fully qualified
 domain name of the tenant.
 
 If you're a [Cloud Solution Provider (CSP)](https://azure.microsoft.com/offers/ms-azr-0145p/), the
-`-Tenant` value **must** be a tenant ID.
+value for the `Tenant` parameter **must** be a tenant ID.
 
 ```azurepowershell-interactive
-Connect-AzAccount -Tenant 'xxxx-xxxx-xxxx-xxxx'
+Connect-AzAccount -Tenant '00000000-0000-0000-0000-000000000000'
 ```
 
 ## Sign in to another Cloud
 
 Azure cloud services offer environments compliant with regional data-handling laws. For accounts in
-a regional cloud, set the environment when you sign in with the `-Environment` argument. This
-parameter works with any sign-in method. For example, if your account is in the China cloud:
+a regional cloud, set the environment when you sign in with the `Environment` parameter. This
+parameter works with any sign-in method. For example, if your account is in Azure China 21Vianet:
 
 ```azurepowershell-interactive
 Connect-AzAccount -Environment AzureChinaCloud

docs-conceptual/azps-5.9.0/az-powershell-proxy.md

@@ -0,0 +1,30 @@
+---
+title: Use the Az PowerShell module behind a proxy
+description: How to use the Azure Az PowerShell module behind a proxy server
+ms.date: 09/27/2021
+ms.devlang: powershell
+ms.topic: conceptual
+ms.custom: devx-track-azurepowershell
+ms.service: azure-powershell
+---
+
+# Use the Az PowerShell module behind a proxy
+
+If a proxy is necessary for HTTP request, the Azure PowerShell team recommends the following proxy
+configuration for different platforms:
+
+|      **Platform**       |                          **Recommended Proxy Settings**                           |                                               **Comment**                                                |
+| ----------------------- | --------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------- |
+| Windows PowerShell 5.1  | System proxy settings                                                             | Do not suggest setting HTTP_PROXY/HTTPS_PROXY environment variables.                                     |
+| PowerShell 7 on Windows | System proxy settings                                                             | Proxy could be configured by setting both HTTP_PROXY and HTTPS_PROXY environment variables.              |
+| PowerShell 7 on macOS   | System proxy settings                                                             | Proxy could be configured by setting both HTTP_PROXY and HTTPS_PROXY environment variables.              |
+| PowerShell 7 on Linux   | Set both HTTP_PROXY and HTTPS_PROXY environment variables, plus optional NO_PROXY | The environment variables should be set before starting PowerShell, otherwise they may not be respected. |
+
+The environment variables used are:
+
+- HTTP_PROXY: the proxy server used on HTTP requests.
+- HTTPS_PROXY: the proxy server used on HTTPS requests.
+- NO_PROXY: a comma-separated list of hostnames that should be excluded from proxying.
+
+On systems where environment variables are case-sensitive, the variable names may be all lowercase
+or all uppercase. The lowercase names are checked first.

docs-conceptual/azps-5.9.0/azureps-in-docker.md

@@ -3,8 +3,8 @@ title: Using Azure PowerShell in Docker
 description: How to use Azure PowerShell that is preinstalled in a Docker image.
 ms.devlang: powershell
 ms.topic: conceptual
-ms.date: 03/20/2020 
-ms.custom: devx-track-azurepowershell 
+ms.date: 09/27/2021
+ms.custom: devx-track-azurepowershell
 ms.service: azure-powershell
 ---
 
@@ -26,7 +26,7 @@ For each new release of the Az module we are releasing an image for the followin
 
 - Ubuntu 18.04 (default)
 - Debian 9
-- CentOs 7
+- CentOS 7
 
 A full list of available images can be found on our [Docker image][az image] page.
 
@@ -47,7 +47,9 @@ PowerShell session.
    docker run -it mcr.microsoft.com/azure-powershell pwsh
    ```
 
-For Windows Docker hosts, you must enable Docker File Sharing to allow local drives on Windows to be shared with Linux containers. For more information see [Get started with Docker for Windows][file-sharing].
+For Windows Docker hosts, you must enable Docker file sharing to allow local drives on Windows to be
+shared with Linux containers. For more information see
+[Get started with Docker for Windows][file-sharing].
 
 ### Run the azure-powershell container interactively using host authentication
 

docs-conceptual/azps-5.9.0/azureps-support-lifecycle.md

@@ -0,0 +1,62 @@
+---
+title: Azure PowerShell support lifecycle
+description: Details about the support lifecycle of the Azure PowerShell modules
+ms.devlang: powershell
+ms.topic: conceptual
+ms.date: 09/29/2021
+ms.custom: devx-track-azurepowershell
+ms.service: azure-powershell
+---
+
+# Azure PowerShell Support Lifecycle
+
+## Az PowerShell modules
+
+The _"Az PowerShell modules"_ are comprised of the module named _"Az"_ and the dependent modules
+signed by _"Microsoft Corporation"_. The Az PowerShell modules are identifiable by their names, that
+starting with _"Az."_. For the current list of Az PowerShell modules, see
+[Azure PowerShell Modules](https://github.com/Azure/azure-powershell/blob/master/documentation/azure-powershell-modules.md).
+
+The Az PowerShell modules support lifecycle falls under the
+[Azure SDK lifecycle policy](https://support.microsoft.com/help/18486). We support no less than the
+last minor version of each of the two most recent major versions of the Az PowerShell module.
+
+## AzureRM PowerShell modules
+
+Because Az PowerShell modules now have all the capabilities of AzureRM PowerShell modules and more,
+we'll retire AzureRM PowerShell modules on 29 February 2024.
+
+To avoid service interruptions, [update your scripts](https://aka.ms/azpsmigrate) that use AzureRM
+PowerShell modules to use Az PowerShell modules by 29 February 2024. To automatically update your
+scripts, follow the
+[quickstart guide](/powershell/azure/quickstart-migrate-azurerm-to-az-automatically).
+
+## Supported environments
+
+The following table identifies the supported platforms for the Az, AzureRM, and Azure PowerShell
+modules.
+
+|        Az        | PowerShell <br/> 7.1.3 | PowerShell <br/> >= 7.0.6 | PowerShell <br/> <= 7.0.5 | Windows PowerShell <br/> 5.1 |
+| :--------------: | :--------------------: | :-----------------------: | :-----------------------: | :--------------------------: |
+|      Az 6.0      |       Supported        |         Supported         |       Not supported       |          Supported           |
+|      Az 5.9      |       Supported        |         Supported         |         Supported         |          Supported           |
+| AzureRM (6.13.2) |     Not Supported      |       Not Supported       |       Not Supported       |          Supported           |
+|  Azure (5.3.1)   |     Not Supported      |       Not Supported       |       Not Supported       |          Supported           |
+
+> [!NOTE]
+> PowerShell 6.2 has reached its end of life as of September 4, 2020. The Az PowerShell modules are
+> not supported on any version of PowerShell 6.
+
+### Information about CVE-2021-26701
+
+The Az PowerShell modules use components impacted by security advisory
+[CVE-2021-26701](https://msrc.microsoft.com/update-guide/vulnerability/CVE-2021-26701) which has
+been fixed in PowerShell 7.0.6 and 7.1.3. For more information, see
+[Microsoft Security Advisory CVE-2021-26701: .NET Core Remote Code Execution Vulnerability](https://github.com/PowerShell/Announcements/issues/23).
+
+Starting with Az 6.0.0, PowerShell 7.0.6 or 7.1.3 or later is required. When the Az.Accounts module
+is imported, the following non-blocking message will be displayed if an unsupported version of
+PowerShell is being used: _"This version of Az.Accounts is only supported on Windows PowerShell 5.1
+and PowerShell 7.0.6 or greater, open
+[https://aka.ms/install-powershell](https://aka.ms/install-powershell) to learn how to upgrade. For
+further information, go to [https://aka.ms/azpslifecyle](https://aka.ms/azpslifecyle)."_

docs-conceptual/azps-5.9.0/azureps-vm-tutorial.yml

@@ -7,7 +7,7 @@ metadata:
     level: Beginner
     displayType: two-column
     interactive: azurepowershell
-    ms.date: 12/13/2018
+    ms.date: 09/07/2021
     ms.author: mirobb
     author: mikefrobbins
     manager: barbkess