Skip to content

Commit e422cbc

Browse files
author
Nicolas Oman
committed
cleanup 2
1 parent ce2911a commit e422cbc

File tree

1 file changed

+1
-0
lines changed

1 file changed

+1
-0
lines changed

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

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -5,6 +5,7 @@ description: How to use managed identities in Azure Service Fabric application c
55
ms.topic: article
66
ms.date: 10/09/2019
77
---
8+
89
# How to leverage a Service Fabric application's managed identity to access Azure services
910

1011
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.

0 commit comments

Comments
 (0)