Refresh of articles (MicrosoftDocs#1923)

Author: mikefrobbins

docs-conceptual/azurermps-6.13.0/authenticate-azureps.md

@@ -1,77 +1,89 @@
 ---
-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.
+title: Sign into Azure with the AzureRM PowerShell module
+description: How to sign into Azure with the AzureRM PowerShell module as a user, service principal, or with managed identities for Azure resources.
 ms.devlang: powershell
 ms.topic: conceptual
-ms.date: 09/09/2018 
+ms.date: 10/05/2021
 ms.custom: devx-track-azurepowershell
 ---
-# Sign in with Azure PowerShell
+# Sign into Azure with the AzureRM PowerShell module
 
 [!INCLUDE [migrate-to-az-banner](../../includes/migrate-to-az-banner.md)]
 
-Azure PowerShell supports several authentication methods. The simplest way to get started is to sign in
-interactively at the command line.
+Azure PowerShell supports several authentication methods. The simplest way to get started is to sign
+in interactively at the command line.
 
 ## Sign in interactively
 
-To sign in interactively, use the [Connect-AzureRmAccount](/powershell/module/azurerm.profile/connect-azurermaccount) cmdlet.
+To sign in interactively, use the
+[Connect-AzureRmAccount](/powershell/module/azurerm.profile/connect-azurermaccount) cmdlet.
 
 ```azurepowershell-interactive
 Connect-AzureRmAccount
 ```
 
-When run, this cmdlet will bring up a dialog box prompting you for your email address and password associated with your Azure account. This authentication lasts for the current PowerShell session.
+When run, this cmdlet will bring up a dialog box prompting you for your email address and password
+associated with your Azure account. This authentication lasts for the current PowerShell session.
 
 > [!IMPORTANT]
-> As of Azure PowerShell 6.3.0, your credentials are shared among multiple PowerShell sessions as long as you remain
-> signed in to Windows. For more information, see the article on [Persistent Credentials](context-persistence.md).
+> As of Azure PowerShell 6.3.0, your credentials are shared among multiple PowerShell sessions as
+> long as you remain signed in to Windows. For more information, see the article on
+> [Persistent Credentials](context-persistence.md).
 
 ## 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 needs, your automation scripts
-stay secure.
+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
+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 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-AzureRmAccount` cmdlet. You'll also need the service principal's sign-in credentials and the tenant ID associated with the service principal. To get the service principal's credentials as the appropriate object, use the [Get-Credential](/powershell/module/microsoft.powershell.security/get-credential) cmdlet. This cmdlet will display a dialog box to enter the service principal user ID and password into.
+To sign in with a service principal, use the `ServicePrincipal` argument with the
+`Connect-AzureRmAccount` cmdlet. You'll also need the service principal's sign-in credentials and
+the tenant ID associated with the service principal. To get the service principal's credentials as
+the appropriate object, use the
+[Get-Credential](/powershell/module/microsoft.powershell.security/get-credential) cmdlet. This
+cmdlet will display a dialog box to enter the service principal user ID and password into.
 
-```azurepowershell-interactive
+```azurepowershell
 $pscredential = Get-Credential
 Connect-AzureRmAccount -ServicePrincipal -Credential $pscredential -TenantId $tenantid
 ```
 
 ## Sign in using an Azure Managed Service Identity
 
-Managed identities for Azure resources is a feature of Azure Active Directory. You can use a managed identity
-service principal for sign-in, and acquire an app-only access token to access other resources. Managed identities are only available on
-virtual machines running in an Azure cloud.
+Managed identities for Azure resources is a feature of Azure Active Directory. You can use a managed
+identity service principal for sign-in, and acquire an app-only access token to access other
+resources. Managed identities are only available on virtual machines running in an Azure cloud.
 
 For more information about managed identities for Azure resources, see
 [How to use managed identities for Azure resources on an Azure VM to acquire an access token](/azure/active-directory/managed-identities-azure-resources/how-to-use-vm-token).
 
 ## Sign in as a Cloud Solution Provider (CSP)
 
-A [Cloud Solution Provider (CSP)](https://azure.microsoft.com/offers/ms-azr-0145p/) sign-in requires the use of `-TenantId`. Normally, this parameter can be provided as either a tenant ID or a domain name. However, for CSP sign-in, it must be provided a **tenant ID**.
+A [Cloud Solution Provider (CSP)](https://azure.microsoft.com/offers/ms-azr-0145p/) sign-in requires
+the use of `TenantId`. Normally, this parameter can be provided as either a tenant ID or a domain
+name. However, for CSP sign-in, it must be provided a **tenant ID**.
 
-```azurepowershell-interactive
-Connect-AzureRmAccount -TenantId 'xxxx-xxxx-xxxx-xxxx'
+```azurepowershell
+Connect-AzureRmAccount -TenantId '00000000-0000-0000-0000-000000000000'
 ```
 
 ## Sign in to another Cloud
 
-Azure cloud services offer environments compliant with regional data-handling regulations.
-For accounts in a regional cloud, set the environment when you sign in with the `-Environment` argument.
+Azure cloud services offer environments compliant with regional data-handling regulations. For
+accounts in a regional cloud, set the environment when you sign in with the `-Environment` argument.
 For example, if your account is in the China cloud:
 
-```azurepowershell-interactive
+```azurepowershell
 Connect-AzureRmAccount -Environment AzureChinaCloud
 ```
 
 The following command gets a list of available environments:
 
-```azurepowershell-interactive
-Get-AzureRmEnvironment | Select-Object Name
+```azurepowershell
+Get-AzureRmEnvironment | Select-Object -Property Name
 ```
 
 ## Learn more about managing Azure role-based access

docs-conceptual/azurermps-6.13.0/azureps-vm-tutorial.yml

@@ -1,20 +1,21 @@
 ### YamlMime:Tutorial
-title: Create virtual machines with the Azure PowerShell
+title: Create virtual machines with the AzureRM PowerShell module
 metadata:
-    title: Create virtual machines with the Azure PowerShell
-    description: Get started with Azure PowerShell by creating virtual machines.
+    title: Create virtual machines with the AzureRM PowerShell module
+    description: Get started with the AzureRM PowerShell module by creating virtual machines.
     audience: Developer
     level: Beginner
     displayType: two-column
     interactive: azurepowershell
-    ms.date: 02/08/2018
-    ms.author: sttramer
-    author: sptramer
-    manager: carmonm
+    ms.date: 10/05/2021
+    ms.author: mirobb
+    author: mikefrobbins
+    manager: barbkess
     ms.devlang: azure-powershell
     ms.prod: powershell
     ms.technology: azure-powershell
     ms.topic: tutorial
+    ms.custom: devx-track-azurepowershell
     clicktale: true
 items:
     - durationInMinutes: 1

docs-conceptual/azurermps-6.13.0/context-persistence.md

@@ -3,7 +3,7 @@ title: Persist user credentials across PowerShell sessions
 description: Learn how to reuse Azure credentials and other information across multiple PowerShell sessions.
 ms.devlang: powershell
 ms.topic: conceptual
-ms.date: 09/09/2018 
+ms.date: 10/05/2021
 ms.custom: devx-track-azurepowershell
 ---
 # Persist user credentials across PowerShell sessions
@@ -40,12 +40,14 @@ a new PowerShell session.
 ## Automatically save the context for the next sign-in
 
 In versions 6.3.0 and later, Azure PowerShell retains your context information automatically between
-sessions. To set PowerShell to forget your context and credentials, use `Disable-AzureRmContextAutoSave`. You'll need to sign in to Azure every time you open a PowerShell session.
+sessions. To set PowerShell to forget your context and credentials, use
+`Disable-AzureRmContextAutoSave`. You'll need to sign in to Azure every time you open a PowerShell
+session.
 
 To allow Azure PowerShell to remember your context after the PowerShell session is closed, use
-`Enable-AzureRmContextAutosave`. Context and credential information are automatically saved in
-a special hidden folder in your user directory (`%AppData%\Roaming\Windows Azure PowerShell`).
-Each new PowerShell session targets the context used in your last session.
+`Enable-AzureRmContextAutosave`. Context and credential information are automatically saved in a
+special hidden folder in your user directory (`%AppData%\Roaming\Windows Azure PowerShell`). Each
+new PowerShell session targets the context used in your last session.
 
 The cmdlets that allow you to manage Azure contexts also allow you fine grained control. If you
 want changes to apply only to the current PowerShell session (`Process` scope) or every PowerShell
@@ -64,34 +66,35 @@ two different ways:
   Most AzureRM cmdlets allow you to pass the context as a parameter to the cmdlet. You can pass a
   context to a background job as shown in the following example:
 
-  ```powershell-interactive
-  PS C:\> $job = Start-Job { param ($ctx) New-AzureRmVm -AzureRmContext $ctx [... Additional parameters ...]} -ArgumentList (Get-AzureRmContext)
+  ```powershell
+ $job = Start-Job { param ($ctx) New-AzureRmVm -AzureRmContext $ctx [... Additional parameters ...]} -ArgumentList (Get-AzureRmContext)
   ```
 
 - Using the default context with Autosave enabled
 
   If you have enabled **Context Autosave**, background jobs automatically use the default saved
   context.
 
-  ```powershell-interactive
-  PS C:\> $job = Start-Job { New-AzureRmVm [... Additional parameters ...]}
+  ```powershell
+  $job = Start-Job { New-AzureRmVm [... Additional parameters ...]}
   ```
 
 When you need to know the outcome of the background task, use `Get-Job` to check the job status and
 `Wait-Job` to wait for the Job to complete. Use `Receive-Job` to capture or display the output of
-the background job. For more information, see [about_Jobs](/powershell/module/microsoft.powershell.core/about/about_jobs).
+the background job. For more information, see
+[about_Jobs](/powershell/module/microsoft.powershell.core/about/about_jobs).
 
 ## Creating, selecting, renaming, and removing contexts
 
-To create a context, you must be signed in to Azure. The `Connect-AzureRmAccount` cmdlet (or its alias,
-`Login-AzureRmAccount`) sets the default context used by Azure PowerShell cmdlets, and
-allows you to access any tenants or subscriptions allowed by your credentials.
+To create a context, you must be signed in to Azure. The `Connect-AzureRmAccount` cmdlet (or its
+alias, `Login-AzureRmAccount`) sets the default context used by Azure PowerShell cmdlets, and allows
+you to access any tenants or subscriptions allowed by your credentials.
 
 To add a new context after sign-in, use `Set-AzureRmContext` (or its alias,
 `Select-AzureRmSubscription`).
 
-```azurepowershell-interactive
-PS C:\> Set-AzureRMContext -Subscription "Contoso Subscription 1" -Name "Contoso1"
+```azurepowershell
+Set-AzureRMContext -Subscription 'Contoso Subscription 1' -Name 'Contoso1'
 ```
 
 The previous example adds a new context targeting 'Contoso Subscription 1' using your current
@@ -100,8 +103,8 @@ default name, using the account ID and subscription ID is used.
 
 To rename an existing context, use the `Rename-AzureRmContext` cmdlet. For example:
 
-```azurepowershell-interactive
-PS C:\> Rename-AzureRmContext '[user1@contoso.org; 123456-7890-1234-564321]` 'Contoso2'
+```azurepowershell
+Rename-AzureRmContext '[user1@contoso.org; 123456-7890-1234-564321]' 'Contoso2'
 ```
 
 This example renames the context with automatic name `[user1@contoso.org; 123456-7890-1234-564321]`
@@ -110,8 +113,8 @@ to quickly select the context.
 
 Finally, to remove a context, use the `Remove-AzureRmContext` cmdlet.  For example:
 
-```azurepowershell-interactive
-PS C:\> Remove-AzureRmContext Contoso2
+```azurepowershell
+Remove-AzureRmContext Contoso2
 ```
 
 Forgets the context that was named 'Contoso2'. You can recreate this context using
@@ -120,12 +123,12 @@ Forgets the context that was named 'Contoso2'. You can recreate this context usi
 ## Removing credentials
 
 You can remove all credentials and associated contexts for a user or service principal using
-`Disconnect-AzureRmAccount` (also known as `Logout-AzureRmAccount`). When executed without parameters,
-the `Disconnect-AzureRmAccount` cmdlet removes all credentials and contexts associated with the User or
-Service Principal in the current context. You may pass in a Username, Service Principal Name, or
-context to target a particular principal.
+`Disconnect-AzureRmAccount` (also known as `Logout-AzureRmAccount`). When executed without
+parameters, the `Disconnect-AzureRmAccount` cmdlet removes all credentials and contexts associated
+with the User or Service Principal in the current context. You may pass in a Username, Service
+Principal Name, or context to target a particular principal.
 
-```azurepowershell-interactive
+```azurepowershell
 Disconnect-AzureRmAccount user1@contoso.org
 ```
 
@@ -134,14 +137,14 @@ Disconnect-AzureRmAccount user1@contoso.org
 Occasionally, you may want to select, change, or remove a context in a PowerShell session without
 impacting other sessions. To change the default behavior of context cmdlets, use the `Scope`
 parameter. The `Process` scope overrides the default behavior by making it apply only for the
-current session. Conversely `CurrentUser` scope changes the context in all sessions, instead of
-just the current session.
+current session. Conversely `CurrentUser` scope changes the context in all sessions, instead of just
+the current session.
 
 As an example, to change the default context in the current PowerShell session without impacting
 other windows, or the context used the next time a session is opened, use:
 
-```azurepowershell-interactive
-PS C:\> Select-AzureRmContext Contoso1 -Scope Process
+```azurepowershell
+Select-AzureRmContext Contoso1 -Scope Process
 ```
 
 ## How the context autosave setting is remembered
@@ -150,11 +153,11 @@ The context AutoSave setting is saved to the user Azure PowerShell directory
 (`%AppData%\Roaming\Windows Azure PowerShell`). Some kinds of computer accounts may not have access
 to this directory. For such scenarios, you can use the environment variable
 
-```azurepowershell-interactive
-$env:AzureRmContextAutoSave="true" | "false"
+```azurepowershell
+$env:AzureRmContextAutoSave=$true
 ```
 
-When set to 'true', the context is automatically saved. If set to 'false', the context isn't saved.
+When set to `$true`, the context is automatically saved. If set to `$false`, the context isn't saved.
 
 ## Changes to the AzureRM.Profile module