Merge pull request #229561 from MicrosoftDocs/main

Publish to live, Monday 4 AM PST, 3/6

Author: ttorble

articles/active-directory/devices/howto-vm-sign-in-azure-ad-linux.md

@@ -107,7 +107,7 @@ Ensure that your client meets the following requirements:
 - TCP connectivity from the client to either the public or private IP address of the VM. (ProxyCommand or SSH forwarding to a machine with connectivity also works.)
 
 > [!IMPORTANT]
-> SSH clients based on PuTTY don't support OpenSSH certificates and can't be used to log in with Azure AD OpenSSH certificate-based authentication.
+> SSH clients based on PuTTY now supports OpenSSH certificates and can be used to log in with Azure AD OpenSSH certificate-based authentication.
 
 ## Enable Azure AD login for a Linux VM in Azure
 

articles/active-directory/multi-tenant-organizations/cross-tenant-synchronization-configure-graph.md

@@ -6,7 +6,6 @@ author: rolyon
 manager: amycolannino
 ms.service: active-directory
 ms.workload: identity
-ms.subservice: multi-tenant-organizations
 ms.topic: how-to
 ms.date: 02/27/2023
 ms.author: rolyon

articles/active-directory/multi-tenant-organizations/cross-tenant-synchronization-configure.md

@@ -6,7 +6,6 @@ author: rolyon
 manager: amycolannino
 ms.service: active-directory
 ms.workload: identity
-ms.subservice: multi-tenant-organizations
 ms.topic: how-to
 ms.date: 02/06/2023
 ms.author: rolyon

articles/active-directory/multi-tenant-organizations/cross-tenant-synchronization-overview.md

@@ -6,7 +6,6 @@ author: rolyon
 manager: amycolannino
 ms.service: active-directory
 ms.workload: identity
-ms.subservice: multi-tenant-organizations
 ms.topic: overview
 ms.date: 02/22/2023
 ms.author: rolyon

articles/active-directory/multi-tenant-organizations/cross-tenant-synchronization-topology.md

@@ -6,7 +6,6 @@ author: rolyon
 manager: amycolannino
 ms.service: active-directory
 ms.workload: identity
-ms.subservice: multi-tenant-organizations
 ms.topic: conceptual
 ms.date: 01/23/2023
 ms.author: rolyon

articles/active-directory/multi-tenant-organizations/overview.md

@@ -6,7 +6,6 @@ author: rolyon
 manager: amycolannino
 ms.service: active-directory
 ms.workload: identity
-ms.subservice: multi-tenant-organizations
 ms.topic: overview
 ms.date: 01/23/2023
 ms.author: rolyon

articles/active-directory/saas-apps/oracle-idcs-for-peoplesoft-tutorial.md

@@ -105,4 +105,4 @@ In this section, you test your Azure AD single sign-on configuration with follow
 
 ## Next steps
 
-Once you configure Oracle IDCS for PeopleSoft you can enforce session control, which protects exfiltration and infiltration of your organization’s sensitive data in real time. Session control extends from Conditional Access. [Learn how to enforce session control with Microsoft Cloud App Security](/cloud-app-security/proxy-deployment-aad).
+Once you configure Oracle IDCS for PeopleSoft you can enforce session control, which protects exfiltration and infiltration of your organization’s sensitive data in real time. Session control extends from Conditional Access. [Learn how to enforce session control with Microsoft Defender for Cloud Apps](/cloud-app-security/proxy-deployment-aad).

articles/aks/use-kms-etcd-encryption.md

@@ -2,7 +2,7 @@
 title: Use Key Management Service (KMS) etcd encryption in Azure Kubernetes Service (AKS) 
 description: Learn how to use the Key Management Service (KMS) etcd encryption with Azure Kubernetes Service (AKS)
 ms.topic: article
-ms.date: 01/17/2023
+ms.date: 02/20/2023
 ---
 
 # Add Key Management Service (KMS) etcd encryption to an Azure Kubernetes Service (AKS) cluster
@@ -338,7 +338,7 @@ Use the following command to disable KMS on existing cluster.
 az aks update --name myAKSCluster --resource-group MyResourceGroup --disable-azure-keyvault-kms
 ```
 
-Use the following command to update all secrets. Otherwise, the old secrets will still be encrypted with the previous key. For larger clusters, you may want to subdivide the secrets by namespace or script an update.
+Use the following command to update all secrets. Otherwise, the old secrets will still be encrypted with the previous key and the encrypt/decrypt permission on key vault is still required. For larger clusters, you may want to subdivide the secrets by namespace or script an update.
 
 ```azurecli-interactive
 kubectl get secrets --all-namespaces -o json | kubectl replace -f -

articles/application-gateway/configuration-listeners.md

@@ -51,8 +51,6 @@ Associate a frontend port. You can select an existing port or create a new one.
 > 
 > **Outbound Rule**: (no specific requirement)
 
-**Limitation**: The portal currently supports private and public listeners creation only for the Public clouds.
-
 ## Protocol
 
 Choose HTTP or HTTPS: