Skip to content

Commit 545fd28

Browse files
authored
Update data-factory-service-identity.md
Remove bullet on blank line
1 parent 003698b commit 545fd28

File tree

1 file changed

+1
-2
lines changed

1 file changed

+1
-2
lines changed

articles/data-factory/data-factory-service-identity.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -25,8 +25,7 @@ Managed identities eliminate the need to manage credentials. Managed identities
2525

2626
There are two types of supported managed identities:
2727

28-
- **System-assigned:** You can enable a managed identity directly on a service instance. When you allow a system-assigned managed identity during the creation of the service, an identity is created in Azure AD tied to that service instance's lifecycle. By design, only that Azure resource can use this identity to request tokens from Azure AD. So when the resource is deleted, Azure automatically deletes the identity for you.
29-
-
28+
- **System-assigned:** You can enable a managed identity directly on a service instance. When you allow a system-assigned managed identity during the creation of the service, an identity is created in Azure AD tied to that service instance's lifecycle. By design, only that Azure resource can use this identity to request tokens from Azure AD. So when the resource is deleted, Azure automatically deletes the identity for you.
3029
- **User-assigned:** You may also create a managed identity as a standalone Azure resource. You can [create a user-assigned managed identity](../active-directory/managed-identities-azure-resources/how-to-manage-ua-identity-portal.md) and assign it to one or more instances of a data factory. In user-assigned managed identities, the identity is managed separately from the resources that use it.
3130

3231
Managed identity provides the below benefits:

0 commit comments

Comments
 (0)