Merge pull request #110474 from Nickomang/release-sf-7.1

Updated (preview) for MI and Request Drain

Author: PRMerger7

articles/service-fabric/concepts-managed-identity.md

@@ -6,7 +6,7 @@ ms.date: 12/09/2019
 ms.custom: sfrev
 ---
 
-# Using Managed identities for Azure with Service Fabric (Preview)
+# Using Managed identities for Azure with Service Fabric
 
 A common challenge when building cloud applications is how to securely manage the credentials in your code for authenticating to various services without saving them locally on a developer workstation or in source control. *Managed identities for Azure* solve this problem for all your resources in Azure Active Directory (Azure AD) by providing them with automatically managed identities within Azure AD. You can use a service's identity to authenticate to any service that supports Azure AD authentication, including Key Vault, without any credentials stored in your code.
 
@@ -42,7 +42,7 @@ Managed identities for Service Fabric are only supported in Azure-deployed Servi
 
 The system-assigned identity of an application is unique to that application; a user-assigned identity is a standalone resource, which may be assigned to multiple applications. Within an application, a single identity (whether system-assigned or user-assigned) can be assigned to multiple services of the application, but each individual service can only be assigned one identity. Lastly, a service must be assigned an identity explicitly to have access to this feature. In effect, the mapping of an application's identities to its constituent services allows for in-application isolation — a service may only use the identity mapped to it.  
 
-Currently, the following scenarios are supported for this preview feature:
+Currently, the following scenarios are supported for this feature:
 
 - Deploy a new application with one or more services and one or more assigned identities
 
@@ -52,12 +52,7 @@ The following scenarios are not supported or not recommended; note these actions
 
 - Remove or change the identities assigned to an application; if you must make changes, submit separate deployments to first add a new identity assignment, and then to remove a previously assigned one. Removal of an identity from an existing application can have undesirable effects, including leaving your application in a state that is not upgradeable. It is safe to delete the application altogether if the removal of an identity is necessary; note this will delete the system-assigned identity (if so defined) associated with the application, and will remove any associations with the user-assigned identities assigned to the application.
 
-- Service Fabric support for managed identities is not integrated at this time into the [AzureServiceTokenProvider](../key-vault/service-to-service-authentication.md); the integration will be achieved by the end of the preview period for the managed identity feature.
-
->
-> [!NOTE]
->
-> This feature is in preview. It may be subject to frequent changes and not suitable for production deployments.
+- Service Fabric support for managed identities is not integrated at this time into the [AzureServiceTokenProvider](../key-vault/service-to-service-authentication.md).
 
 ## Next steps
 

articles/service-fabric/configure-new-azure-service-fabric-enable-managed-identity.md

@@ -6,7 +6,7 @@ ms.date: 12/09/2019
 ms.custom: sfrev
 ---
 
-# Configure managed identity support for a new Service Fabric cluster (preview)
+# Configure managed identity support for a new Service Fabric cluster
 
 To use [Managed identities for Azure resources](../active-directory/managed-identities-azure-resources/overview.md) in your Service Fabric applications, first enable the *Managed Identity Token Service* on the cluster. This service is responsible for the authentication of Service Fabric applications using their managed identities, and for obtaining access tokens on their behalf. Once the service is enabled, you can see it in Service Fabric Explorer under the **System** section in the left pane, running under the name **fabric:/System/ManagedIdentityTokenService** next to other system services.
 

articles/service-fabric/how-to-deploy-service-fabric-application-system-assigned-managed-identity.md

@@ -6,7 +6,7 @@ ms.topic: article
 ms.date: 07/25/2019
 ---
 
-# Deploy Service Fabric application with system-assigned managed identity (preview)
+# Deploy Service Fabric application with system-assigned managed identity
 
 In order to access the managed identity feature for Azure Service Fabric applications, you must first enable the Managed Identity Token Service on the cluster. This service is responsible for the authentication of Service Fabric applications using their managed identities, and for obtaining access tokens on their behalf. Once the service is enabled, you can see it in Service Fabric Explorer under the **System** section in the left pane, running under the name **fabric:/System/ManagedIdentityTokenService** next to other system services.
 

articles/service-fabric/how-to-deploy-service-fabric-application-user-assigned-managed-identity.md

@@ -5,7 +5,7 @@ description: This article shows you how to deploy Service Fabric application wit
 ms.topic: article
 ms.date: 12/09/2019
 ---
-# Deploy Service Fabric application with a User-Assigned Managed Identity (preview)
+# Deploy Service Fabric application with a User-Assigned Managed Identity
 
 To deploy a Service Fabric application with managed identity, the application needs to be deployed through Azure Resource Manager, typically with an Azure Resource Manager template. For more information on how to deploy Service Fabric application through Azure Resource Manager, see [Manage applications and services as Azure Resource Manager resources](service-fabric-application-arm-resource.md).
 

articles/service-fabric/how-to-managed-identity-service-fabric-app-code.md

@@ -1,12 +1,12 @@
 ---
 title: Use managed identity with an application
-description: How to use managed identities in Azure Service Fabric application code to access Azure Services. This feature is in public preview.
+description: How to use managed identities in Azure Service Fabric application code to access Azure Services.
 
 ms.topic: article
 ms.date: 10/09/2019
 ---
 
-# How to leverage a Service Fabric application's managed identity to access Azure services  
+# How to leverage a Service Fabric application's managed identity to access Azure services
 
 Service Fabric applications can leverage managed identities to access other Azure resources which support Azure Active Directory-based authentication. An application can obtain an [access token](../active-directory/develop/developer-glossary.md#access-token) representing its identity, which may be system-assigned or user-assigned, and use it as a 'bearer' token to authenticate itself to another service - also known as a [protected resource server](../active-directory/develop/developer-glossary.md#resource-server). The token represents the identity assigned to the Service Fabric application, and will only be issued to Azure resources (including SF applications) which share that identity. Refer to the [managed identity overview](../active-directory/managed-identities-azure-resources/overview.md) documentation for a detailed description of managed identities, as well as the distinction between system-assigned and user-assigned identities. We will refer to a managed-identity-enabled Service Fabric application as the [client application](../active-directory/develop/developer-glossary.md#client-application) throughout this article.