Merge pull request #192950 from MicrosoftDocs/main

3/25 AM Publish

Author: huypub

articles/active-directory/authentication/concept-sspr-writeback.md

@@ -156,6 +156,9 @@ Passwords aren't written back in any of the following situations:
 > [!WARNING]
 > Use of the checkbox "User must change password at next logon" in on-premises AD DS administrative tools like Active Directory Users and Computers or the Active Directory Administrative Center is supported as a preview feature of Azure AD Connect. For more information, see [Implement password hash synchronization with Azure AD Connect sync](../hybrid/how-to-connect-password-hash-synchronization.md).
 
+> [!NOTE]
+> If a user has the option "Password never expires" set in Active Directory (AD), the force password change flag will not be set in Active Directory (AD), so the user will not be prompted to change the password during the next sign-in even if the option to force the user to change their password on next logon option is selected during an administrator-initiated end-user password reset.
+
 ## Next steps
 
 To get started with SSPR writeback, complete the following tutorial:

articles/active-directory/enterprise-users/licensing-service-plan-reference.md

@@ -6,7 +6,7 @@ ms.assetid: ef2797d7-d440-4a9a-a648-db32ad137494
 ms.service: active-directory
 ms.topic: reference
 ms.workload: identity
-ms.date: 1/31/2022
+ms.date: 3/24/2022
 ms.subservice: hybrid
 ms.author: rodejo
 ms.custom: has-adal-ref
@@ -82,10 +82,9 @@ To read more about auto-upgrade, see [Azure AD Connect: Automatic upgrade](how-t
 ### Release status
 3/24/2022: Released for download only, not available for auto upgrade
 
-
 ### Bug fixes
  - Fixed an issue where some sync rule functions were not parsing surrogate pairs properly.
- - Fixed an issue where, under certain circumstances, the sync service would not start due to a model db corruption.
+ - Fixed an issue where, under certain circumstances, the sync service would not start due to a model db corruption. You can read more about the model db corroption issue in [this article](https://docs.microsoft.com/troubleshoot/azure/active-directory/resolve-model-database-corruption-sqllocaldb)
 
 ## 2.0.91.0
 

articles/active-directory/hybrid/reference-connect-version-history.md

@@ -9,7 +9,7 @@ ms.service: active-directory
 ms.subservice: app-mgmt
 ms.topic: quickstart
 ms.workload: identity
-ms.date: 09/22/2021
+ms.date: 03/24/2022
 ms.author: davidmu
 ms.reviewer: alamaral
 ms.custom: mode-other

articles/active-directory/manage-apps/add-application-portal-assign-users.md

@@ -9,7 +9,7 @@ ms.service: active-directory
 ms.subservice: app-mgmt
 ms.topic: quickstart
 ms.workload: identity
-ms.date: 09/22/2021
+ms.date: 03/24/2022
 ms.author: davidmu
 ms.reviewer: ergleenl
 ms.custom: mode-other

articles/active-directory/manage-apps/add-application-portal.md

@@ -9,7 +9,7 @@ ms.service: active-directory
 ms.subservice: app-mgmt
 ms.topic: quickstart
 ms.workload: identity
-ms.date: 09/22/2021
+ms.date: 03/24/2022
 ms.author: davidmu
 ms.reviewer: ergleenl
 ms.custom: mode-other

articles/active-directory/manage-apps/delete-application-portal.md

@@ -9,7 +9,7 @@ ms.service: active-directory
 ms.subservice: app-mgmt
 ms.workload: identity
 ms.topic: quickstart
-ms.date: 09/07/2021
+ms.date: 03/24/2022
 ms.author: davidmu
 ms.reviewer: arvinh
 ms.custom: mode-other
@@ -45,15 +45,15 @@ To view the enterprise applications registered in your tenant:
 
 To search for a particular application:
 
-1. In the **Application Type** menu, select **All applications**, and choose **Apply**.
+1. Select the **Application Type** filter option. Select **All applications** from the **Application Type** drop-down menu, and choose **Apply**.
 1. Enter the name of the application you want to find. If the application has been added to your Azure AD tenant, it appears in the search results. For example, you can search for the **Azure AD SAML Toolkit 1** application that is used in the previous quickstarts. 
 1. Try entering the first few letters of an application name.
 
 ## Select viewing options
 
 Select options according to what you're looking for:
 
-1. You can view the applications by **Application Type**, **Application Status**, and **Application visibility**.
+1. You can view the applications by **Application Type**, **Application Status**, and **Application visibility**. These three options are the default filters. 
 1. Under **Application Type**, choose one of these options:
     - **Enterprise Applications** shows non-Microsoft applications.
     - **Microsoft Applications** shows Microsoft applications.
@@ -62,6 +62,14 @@ Select options according to what you're looking for:
 1. Under **Application Status**, choose **Any**, **Disabled**, or **Enabled**. The **Any** option includes both disabled and enabled applications.
 1. Under **Application Visibility**, choose **Any**, or **Hidden**. The **Hidden** option shows applications that are in the tenant, but aren't visible to users.
 1. After choosing the options you want, select **Apply**.
+1. Select **Add filters** to add more options for filtering the search results. The other that exist are:
+   - **Application ID**
+   - **Created on**
+   - **Assignment required**
+   - **Is App Proxy**
+   - **Owner**
+1. To remove any of the filter options already added, select the **X** icon next to the filter option.
+
 
 ## Clean up resources
 

articles/active-directory/manage-apps/media/view-applications-portal/view-enterprise-applications.png

@@ -3,7 +3,7 @@ title: Use Container Storage Interface (CSI) drivers for Azure Files on Azure Ku
 description: Learn how to use the Container Storage Interface (CSI) drivers for Azure Files in an Azure Kubernetes Service (AKS) cluster.
 services: container-service
 ms.topic: article
-ms.date: 03/22/2021
+ms.date: 03/24/2021
 author: palma21
 
 ---
@@ -112,6 +112,9 @@ storageclass.storage.k8s.io/my-azurefile created
 
 The Azure Files CSI driver supports creating [snapshots of persistent volumes](https://kubernetes-csi.github.io/docs/snapshot-restore-feature.html) and the underlying file shares.
 
+> [!NOTE]
+> This driver only supports snapshot creation, restore from snapshot is not supported by this driver, snapshot could be restored from Azure portal or CLI. To get the snapshot created, you can go to Azure Portal -> access the Storage Account -> File shares -> access the file share associated -> Snapshots. There you can click on it and restore. 
+
 Create a [volume snapshot class](https://github.com/kubernetes-sigs/azurefile-csi-driver/blob/master/deploy/example/snapshot/volumesnapshotclass-azurefile.yaml) with the [kubectl apply][kubectl-apply] command:
 
 ```console

articles/active-directory/manage-apps/view-applications-portal.md

@@ -111,7 +111,7 @@ You now have a running pod with an Azure Files share mounted at */mnt/azure*. Yo
 
 ## Mount file share as a persistent volume
  - Mount options
-> The default value for *fileMode* and *dirMode* is *0777* for Kubernetes version 1.15 and above.
+> The default value for *fileMode* and *dirMode* is *0777*.
 
 ```yaml
 apiVersion: v1
@@ -156,6 +156,7 @@ spec:
   accessModes:
     - ReadWriteMany
   storageClassName: ""
+  volumeName: azurefile
   resources:
     requests:
       storage: 5Gi
@@ -195,10 +196,6 @@ kubectl delete pod mypod
 kubectl apply -f azure-files-pod.yaml
 ```
 
-## Using Azure tags
-
-For more details on using Azure tags, see [Use Azure tags in Azure Kubernetes Service (AKS)][use-tags].
-
 ## Next steps
 
 For Azure File CSI driver parameters, see [CSI driver parameters][CSI driver parameters].