Merge pull request #184597 from MicrosoftDocs/master

1/10 AM Publish

Author: huypub

articles/active-directory/app-proxy/application-proxy-faq.yml

@@ -118,6 +118,12 @@ sections:
           HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\WinHttp\EnableDefaultHttp2 (DWORD) Value: 0 
           ```
           
+      - question: |
+         Why is the connector still showing in Azure AD portal after I uninstalled the connector from the Server?
+        answer: |
+           When a connector is running, it remains active as it connects to the service. Uninstalled /Unused connectors are tagged as inactive and are removed after 10 days of inactivity from the portal.
+           There is no way to remove the Inactive connector manually from the Azure portal.
+          
   - name: Application configuration
     questions:
       - question: |

articles/aks/azure-disk-customer-managed-keys.md

@@ -3,7 +3,7 @@ title: Use a customer-managed key to encrypt Azure disks in Azure Kubernetes Ser
 description: Bring your own keys (BYOK) to encrypt AKS OS and Data disks.
 services: container-service
 ms.topic: article
-ms.date: 09/01/2020
+ms.date: 1/9/2022
 
 ---
 
@@ -121,10 +121,10 @@ Create a file called **byok-azure-disk.yaml** that contains the following inform
 kind: StorageClass
 apiVersion: storage.k8s.io/v1  
 metadata:
-  name: hdd
-provisioner: kubernetes.io/azure-disk
+  name: byok
+provisioner: disk.csi.azure.com # replace with "kubernetes.io/azure-disk" if aks version is less than 1.21
 parameters:
-  skuname: Standard_LRS
+  skuname: StandardSSD_LRS
   kind: managed
   diskEncryptionSetID: "/subscriptions/{myAzureSubscriptionId}/resourceGroups/{myResourceGroup}/providers/Microsoft.Compute/diskEncryptionSets/{myDiskEncryptionSetName}"
 ```

articles/aks/azure-files-dynamic-pv.md

@@ -34,7 +34,7 @@ A storage class is used to define how an Azure file share is created. A storage
 * *Premium_ZRS* - premium zone redundant storage (ZRS)
 
 > [!NOTE]
-> Azure Files support premium storage in AKS clusters that run Kubernetes 1.13 or higher, minimum premium file share is 100GB
+> minimum premium file share is 100GB
 
 For more information on Kubernetes storage classes for Azure Files, see [Kubernetes Storage Classes][kubernetes-storage-classes].
 
@@ -45,7 +45,7 @@ kind: StorageClass
 apiVersion: storage.k8s.io/v1
 metadata:
   name: my-azurefile
-provisioner: kubernetes.io/azure-file
+provisioner: file.csi.azure.com # replace with "kubernetes.io/azure-file" if aks version is less than 1.21
 mountOptions:
   - dir_mode=0777
   - file_mode=0777
@@ -171,7 +171,7 @@ kind: StorageClass
 apiVersion: storage.k8s.io/v1
 metadata:
   name: my-azurefile
-provisioner: kubernetes.io/azure-file
+provisioner: file.csi.azure.com # replace with "kubernetes.io/azure-file" if aks version is less than 1.21
 mountOptions:
   - dir_mode=0777
   - file_mode=0777

articles/aks/certificate-rotation.md

@@ -3,7 +3,7 @@ title: Rotate certificates in Azure Kubernetes Service (AKS)
 description: Learn how to rotate your certificates in an Azure Kubernetes Service (AKS) cluster.
 services: container-service
 ms.topic: article
-ms.date: 11/03/2021
+ms.date: 1/9/2022
 ---
 
 # Rotate certificates in Azure Kubernetes Service (AKS)
@@ -28,7 +28,7 @@ AKS generates and uses the following certificates, Certificate Authorities, and
 * The `kubectl` client has a certificate for communicating with the AKS cluster.
 
 > [!NOTE]
-> AKS clusters created prior to May 2019 have certificates that expire after two years. Any cluster created after May 2019 or any cluster that has its certificates rotated have Cluster CA certificates that expire after 30 years. All other AKS certificates, which use the Cluster CA to for signing, will expire after two years and are automatically rotated during AKS version upgrade. To verify when your cluster was created, use `kubectl get nodes` to see the *Age* of your node pools.
+> AKS clusters created prior to May 2019 have certificates that expire after two years. Any cluster created after May 2019 or any cluster that has its certificates rotated have Cluster CA certificates that expire after 30 years. All other AKS certificates, which use the Cluster CA to for signing, will expire after two years and are automatically rotated during AKS version upgrade happened after 8/1/2021. To verify when your cluster was created, use `kubectl get nodes` to see the *Age* of your node pools.
 > 
 > Additionally, you can check the expiration date of your cluster's certificate. For example, the following bash command displays the client certificate details for the *myAKSCluster* cluster in resource group *rg*
 > ```console

articles/aks/intro-kubernetes.md

@@ -16,7 +16,7 @@ You can create an AKS cluster using:
 * [The Azure CLI](kubernetes-walkthrough.md)
 * [The Azure portal](kubernetes-walkthrough-portal.md)
 * [Azure PowerShell](kubernetes-walkthrough-powershell.md)
-* Using template-driven deployment options, like [Azure Resource Manager templates](kubernetes-walkthrough-rm-template.md) and Terraform 
+* Using template-driven deployment options, like [Azure Resource Manager templates](kubernetes-walkthrough-rm-template.md), [Bicep](../azure-resource-manager/bicep/overview.md) and Terraform 
 
 When you deploy an AKS cluster, the Kubernetes master and all nodes are deployed and configured for you. Advanced networking, Azure Active Directory (Azure AD) integration, monitoring, and other features can be configured during the deployment process. 
 
@@ -174,4 +174,4 @@ Learn more about deploying and managing AKS with the Azure CLI Quickstart.
 [kubernetes-rbac]: concepts-identity.md#kubernetes-rbac
 [concepts-identity]: concepts-identity.md
 [concepts-storage]: concepts-storage.md
-[conf-com-node]: ../confidential-computing/confidential-nodes-aks-overview.md
+[conf-com-node]: ../confidential-computing/confidential-nodes-aks-overview.md

articles/aks/use-ultra-disks.md

@@ -3,7 +3,7 @@ title: Enable Ultra Disk support on Azure Kubernetes Service (AKS)
 description: Learn how to enable and configure Ultra Disks in an Azure Kubernetes Service (AKS) cluster
 services: container-service
 ms.topic: article
-ms.date: 10/12/2021
+ms.date: 1/9/2022
 
 ---
 
@@ -67,12 +67,12 @@ kind: StorageClass
 apiVersion: storage.k8s.io/v1
 metadata:
   name: ultra-disk-sc
-provisioner: kubernetes.io/azure-disk
+provisioner: disk.csi.azure.com # replace with "kubernetes.io/azure-disk" if aks version is less than 1.21
 volumeBindingMode: WaitForFirstConsumer # optional, but recommended if you want to wait until the pod that will use this disk is created 
 parameters:
   skuname: UltraSSD_LRS
   kind: managed
-  cachingmode: None
+  cachingMode: None
   diskIopsReadWrite: "2000"  # minimum value: 2 IOPS/GiB 
   diskMbpsReadWrite: "320"   # minimum value: 0.032/GiB
 ```

articles/azure-netapp-files/configure-kerberos-encryption.md

@@ -12,7 +12,7 @@ ms.service: azure-netapp-files
 ms.workload: storage
 ms.tgt_pltfrm: na
 ms.topic: how-to
-ms.date: 01/07/2022
+ms.date: 01/10/2022
 ms.author: anfdocs
 ---
 # Configure NFSv4.1 Kerberos encryption for Azure NetApp Files
@@ -27,6 +27,7 @@ The following requirements apply to NFSv4.1 client encryption:
 * DNS A/PTR record creation for both the client and Azure NetApp Files NFS server IP addresses
 * A Linux client: This article provides guidance for RHEL and Ubuntu clients.  Other clients will work with similar configuration steps. 
 * NTP server access: You can use one of the commonly used Active Directory Domain Controller (AD DC) domain controllers.
+* To leverage Domain or LDAP user authentication, ensure that NFSv4.1 volumes are enabled for LDAP. See [Configure ADDS LDAP with extended groups](configure-ldap-extended-groups.md).
 * Ensure that User Principal Names for user accounts do *not* end with a `$` symbol (for example, user$@REALM.COM). <!-- Not using 'contoso.com' in this example; per Mark, A customers REALM namespace may be different from their AD domain name space. -->   
     For [Group managed service accounts](/windows-server/security/group-managed-service-accounts/getting-started-with-group-managed-service-accounts) (gMSA), you need to remove the trailing `$` from the User Principal Name before the account can be used with the Azure NetApp Files Kerberos feature.
 

articles/cognitive-services/Speech-Service/how-to-migrate-to-custom-neural-voice.md

@@ -15,7 +15,7 @@ ms.author: v-baolianzou
 # Migrate from custom voice to custom neural voice
 
 > [!IMPORTANT]
-> We are retiring the standard/non-neural training tier of custom voice on February 29, 2024. During the retiring period (3/1/2021 - 2/29/2024), existing standard tier users can continue to use their non-neural models created, but all new users who sign up for speech resources from **3/1/2021** should move to the neural tier/custom neural voice. After 2/29/2024, all standard/non-neural custom voices will no longer be supported. 
+> We are retiring the standard non-neural training tier of custom voice from March 1, 2021 through February 29, 2024. If you used a non-neural custom voice with your Speech resource prior to March 1, 2021 then you can continue to do so until February 29, 2024. All other Speech resources can only use custom neural voice. After February 29, 2024, the non-neural custom voices won't be supported with any Speech resource. 
 
 The custom neural voice lets you build higher-quality voice models while requiring less data. You can develop more realistic, natural, and conversational voices. Your customers and end users will benefit from the latest Text-to-Speech technology, in a responsible way. 
 

articles/cognitive-services/Speech-Service/how-to-migrate-to-prebuilt-neural-voice.md

@@ -15,7 +15,7 @@ ms.author: v-baolianzou
 # Migrate from prebuilt standard voice to prebuilt neural voice
 
 > [!IMPORTANT]
-> We are retiring the standard voices on August 31, 2024. During the retiring period (9/1/2021 - 8/31/2024), existing standard voice users can continue to use standard voices, but all new users who sign up for speech resources from **9/1/2021** should choose [neural voice names](language-support.md#prebuilt-neural-voices) in your speech synthesis request. After 8/31/2024, the standard voices will no longer be supported in your speech synthesis request. 
+> We are retiring the standard voices from September 1, 2021 through August 31, 2024. If you used a standard voice with your Speech resource prior to September 1, 2021 then you can continue to do so until August 31, 2024. All other Speech resources can only use prebuilt neural voices. You can choose from the supported [neural voice names](language-support.md#prebuilt-neural-voices). After August 31, the standard voices won't be supported with any Speech resource.
 
 The prebuilt neural voice provides more natural sounding speech output, and thus, a better end-user experience. 
 

articles/cognitive-services/Speech-Service/migration-overview-neural-voice.md

@@ -19,7 +19,7 @@ We're retiring two features from [Text-to-Speech](index-text-to-speech.yml) capa
 ## Custom voice (non-neural training)
 
 > [!IMPORTANT]
-> We are retiring the standard/non-neural training tier of custom voice on February 29, 2024. During the retiring period (3/1/2021 - 2/29/2024), existing standard tier users can continue to use their non-neural models created, but all new users who sign up for speech resources from **3/1/2021** should move to the neural tier/custom neural voice. After 2/29/2024, all standard/non-neural custom voices will no longer be supported. 
+> We are retiring the standard non-neural training tier of custom voice from March 1, 2021 through February 29, 2024. If you used a non-neural custom voice with your Speech resource prior to March 1, 2021 then you can continue to do so until February 29, 2024. All other Speech resources can only use custom neural voice. After February 29, 2024, the non-neural custom voices won't be supported with any Speech resource. 
 
 Go to [this article](how-to-migrate-to-custom-neural-voice.md) to learn how to migrate to custom neural voice. 
 
@@ -32,7 +32,7 @@ Go to the [pricing page](https://azure.microsoft.com/pricing/details/cognitive-s
 ## Prebuilt standard voice
 
 > [!IMPORTANT]
-> We are retiring the standard voices on August 31, 2024. During the retiring period (9/1/2021 - 8/31/2024), existing standard voice users can continue to use standard voices, but all new users who sign up for speech resources from **9/1/2021** should choose [neural voice names](language-support.md#prebuilt-neural-voices) in your speech synthesis request. After 8/31/2024, the standard voices will no longer be supported in your speech synthesis request. 
+> We are retiring the standard voices from September 1, 2021 through August 31, 2024. If you used a standard voice with your Speech resource prior to September 1, 2021 then you can continue to do so until August 31, 2024. All other Speech resources can only use prebuilt neural voices. You can choose from the supported [neural voice names](language-support.md#prebuilt-neural-voices). After August 31, the standard voices won't be supported with any Speech resource.
 
 Go to [this article](how-to-migrate-to-prebuilt-neural-voice.md) to learn how to migrate to prebuilt neural voice.