Update storage-auth-user-delegation-include.md

Author: tamram

includes/storage-auth-user-delegation-include.md

@@ -5,20 +5,17 @@ services: storage
 author: tamram
 ms.service: storage
 ms.topic: "include"
-ms.date: 07/25/2019
+ms.date: 01/15/2020
 ms.author: tamram
 ms.custom: "include file"
 ---
 
-## About the user delegation SAS (preview)
+## About the user delegation SAS
 
 A SAS token for access to a container or blob may be secured by using either Azure AD credentials or an account key. A SAS secured with Azure AD credentials is called a user delegation SAS, because the OAuth 2.0 token used to sign the SAS is requested on behalf of the user.
 
 Microsoft recommends that you use Azure AD credentials when possible as a security best practice, rather than using the account key, which can be more easily compromised. When your application design requires shared access signatures, use Azure AD credentials to create a user delegation SAS for superior security. For more information about the user delegation SAS, see [Create a user delegation SAS](/rest/api/storageservices/create-user-delegation-sas).
 
-> [!NOTE]
-> The user delegation SAS preview is intended for non-production use only.
-
 > [!CAUTION]
 > Any client that possesses a valid SAS can access data in your storage account as permitted by that SAS. It's important to protect a SAS from malicious or unintended use. Use discretion in distributing a SAS, and have a plan in place for revoking a compromised SAS.