Merge pull request #216705 from MicrosoftDocs/main

Publish to live, Tuesday 4 AM PST, 11/1

Author: ttorble

.openpublishing.redirection.json

@@ -29353,6 +29353,11 @@
             "source_path_from_root": "/articles/application-gateway/configuration-front-end-ip.md",
             "redirect_url": "/azure/application-gateway/configuration-frontend-ip",
             "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/virtual-network/ip-services/create-custom-ip-address-prefix-ipv6.md",
+            "redirect_url": "/azure/virtual-network/ip-services/create-custom-ip-address-prefix-ipv6-powershell",
+            "redirect_document_id": false
         }
     ]
 }

articles/active-directory/hybrid/how-to-connect-install-prerequisites.md

@@ -83,7 +83,8 @@ We recommend that you harden your Azure AD Connect server to decrease the securi
 - Follow these [additional guidelines](/windows-server/identity/ad-ds/plan/security-best-practices/reducing-the-active-directory-attack-surface) to reduce the attack surface of your Active Directory environment.
 - Follow the [Monitor changes to federation configuration](how-to-connect-monitor-federation-changes.md) to setup alerts to monitor changes to the trust established between your Idp and Azure AD. 
 - Enable Multi Factor Authentication (MFA) for all users that have privileged access in Azure AD or in AD. One security issue with using AADConnect is that if an attacker can get control over the Azure AD Connect server they can manipulate users in Azure AD. To prevent a attacker from using these capabilities to take over Azure AD accounts, MFA offers protections so that even if an attacker manages to e.g. reset a user's password using Azure AD Connect they still cannot bypass the second factor.
-- Disable Soft Matching on your tenant. Soft Matching is a great feature to help transfering source of autority for existing cloud only objects to Azure AD Connect, but it comes with certain security risks. If you do not require it, you should [disable Soft Matching](how-to-connect-syncservice-features.md#blocksoftmatch)
+- Disable Soft Matching on your tenant. Soft Matching is a great feature to help transfering source of autority for existing cloud managed objects to Azure AD Connect, but it comes with certain security risks. If you do not require it, you should [disable Soft Matching](how-to-connect-syncservice-features.md#blocksoftmatch).
+- Disable Hard Match Takeover. Hard match takeover allows Azure AD Connect to take control of a cloud managed object and changing the source of authority for the object to Active Directory. Once the source of authority of an object is taken over by Azure AD Connect, changes made to the Active Directory object that is linked to the Azure AD object will overwrite the original Azure AD data - including the password hash, if Password Hash Sync is enabled. An attacker could use this capability to take over control of cloud managed objects. To mitigate this risk, [disable hard match takeover](https://learn.microsoft.com/powershell/module/msonline/set-msoldirsyncfeature?view=azureadps-1.0#example-3-block-cloud-object-takeover-through-hard-matching-for-the-tenant).
 
 ### SQL Server used by Azure AD Connect
 * Azure AD Connect requires a SQL Server database to store identity data. By default, a SQL Server 2019 Express LocalDB (a light version of SQL Server Express) is installed. SQL Server Express has a 10-GB size limit that enables you to manage approximately 100,000 objects. If you need to manage a higher volume of directory objects, point the installation wizard to a different installation of SQL Server. The type of SQL Server installation can impact the [performance of Azure AD Connect](./plan-connect-performance-factors.md#sql-database-factors).

articles/automation/automation-availability-zones.md

@@ -33,7 +33,7 @@ In the event when a zone is down, there's no action required by you to recover f
 ## Supported regions with availability zones
 
 See [Regions and Availability Zones in Azure](../availability-zones/az-overview.md) for the Azure regions that have availability zones. 
-Automation accounts currently support the following regions in preview: 
+Automation accounts currently support the following regions: 
 
 - China North 3
 - Qatar Central

articles/automation/whats-new.md

@@ -24,9 +24,13 @@ This page is updated monthly, so revisit it regularly. If you're looking for ite
 
 ## October 2022
 
+### Public preview of PowerShell 7.2 and Python 3.10
+
+Azure Automation now supports runbooks in latest Runtime versions - PowerShell 7.2 and Python 3.10 in public preview. This enables creation and execution of runbooks for orchestration of management tasks. These new runtimes are currently supported only for Cloud jobs in five regions - West Central US, East US, South Africa North, North Europe, Australia, and Southeast. [Learn more](automation-runbook-types.md).
+
 ### Guidance for Disaster Recovery of Azure Automation account
 
-Azure Automation now supports you to build your own disaster recovery strategy to handle a region-wide or zone-wide failure. [Learn more](https://learn.microsoft.com/azure/automation/automation-disaster-recovery).
+Build your own disaster recovery strategy to handle a region-wide or zone-wide failure [Learn more](https://learn.microsoft.com/azure/automation/automation-disaster-recovery).
 
 ## September 2022
 

articles/azure-arc/servers/ssh-arc-overview.md

@@ -19,7 +19,7 @@ allowing existing management tools to have a greater impact on Azure Arc-enabled
 SSH access to Arc-enabled servers provides the following key benefits:
  - No public IP address or open SSH ports required
  - Access to Windows and Linux machines
- - Ability to log-in as a local user or an [Azure user (Linux only)](../../active-directory/devices/howto-vm-sign-in-azure-ad-linux.md)
+ - Ability to log in as a local user or an [Azure user (Linux only)](../../active-directory/devices/howto-vm-sign-in-azure-ad-linux.md)
  - Support for other OpenSSH based tooling with config file support
 
 ## Prerequisites
@@ -42,32 +42,54 @@ SSH access to Arc-enabled servers is currently supported in the following region
    - Ubuntu Server: Ubuntu Server 16.04 to Ubuntu Server 20.04
 
 ## Getting started
-### Register the HybridConnectivity resource provider
+
+### Install local command line tool
+This functionality is currently packaged in an Azure CLI extension and an Azure PowerShell module.
+#### [Install Azure CLI extension](#tab/azure-cli)
+
+```az extension add --name ssh```
+
 > [!NOTE]
-> This is a one-time operation that needs to be performed on each subscription.
+> The Azure CLI extension version must be greater than 1.1.0.
 
-Check if the HybridConnectivity resource provider (RP) has been registered:
+#### [Install Azure PowerShell module](#tab/azure-powershell)
 
-```az provider show -n Microsoft.HybridConnectivity```
+```Install-Module -Name AzPreview -Scope CurrentUser -Repository PSGallery -Force```
 
-If the RP has not been registered, run the following:
+### Enable functionality on your Arc-enabled server
+In order to use the SSH connect feature, you must enable connections on the hybrid agent.
 
-```az provider register -n Microsoft.HybridConnectivity```
+> [!NOTE]
+> The following actions must be completed in an elevated terminal session.
 
-This operation can take 2-5 minutes to complete.  Before moving on, check that the RP has been registered.
+View your current incoming connections:
 
-### Install az CLI extension
-This functionality is currently package in an az CLI extension.
-In order to install this extension, run:
+```azcmagent config list```
 
-```az extension add --name ssh```
+If you have existing ports, you'll need to include them in the following command.
 
-If you already have the extension installed, it can be updated by running:
+To add access to SSH connections, run the following:
 
-```az extension update --name ssh```
+```azcmagent config set incomingconnections.ports 22<,other open ports,...>```
+
+If you're using a non-default port for your SSH connection, replace port 22 with your desired port in the previous command.
 
 > [!NOTE]
-> The Azure CLI extension version must be greater than 1.1.0.
+> The following steps will not need to be run for most users.
+
+### Register the HybridConnectivity resource provider
+> [!NOTE]
+> This is a one-time operation that needs to be performed on each subscription.
+
+Check if the HybridConnectivity resource provider (RP) has been registered:
+
+```az provider show -n Microsoft.HybridConnectivity```
+
+If the RP hasn't been registered, run the following:
+
+```az provider register -n Microsoft.HybridConnectivity```
+
+This operation can take 2-5 minutes to complete.  Before moving on, check that the RP has been registered.
 
 ### Create default connectivity endpoint
 > [!NOTE]
@@ -86,24 +108,5 @@ Validate endpoint creation:
  az rest --method get --uri https://management.azure.com/subscriptions/<subscription>/resourceGroups/<resourcegroup>/providers/Microsoft.HybridCompute/machines/<arc enabled server name>/providers/Microsoft.HybridConnectivity/endpoints/default?api-version=2021-10-06-preview
  ```
 
-### Enable functionality on your Arc-enabled server
-In order to use the SSH connect feature, you must enable connections on the hybrid agent.
-
-> [!NOTE]
-> The following actions must be completed in an elevated terminal session.
-
-View your current incoming connections:
-
-```azcmagent config list```
-
-If you have existing ports, you will need to include them in the following command.
-
-To add access to SSH connections, run the following:
-
-```azcmagent config set incomingconnections.ports 22<,other open ports,...>```
-
-> [!NOTE]
-> If you are using a non-default port for your SSH connection, replace port 22 with your desired port in the previous command.
-
 ## Examples
-To view examples of using the ```az ssh arc``` command, view the az CLI documentation page for [az ssh](/cli/azure/ssh).
+To view examples, view the Az CLI documentation page for [az ssh](/cli/azure/ssh) or the Azure PowerShell documentation page for [Az.Ssh](/powershell/module/az.ssh).