Skip to content

Commit f10b7c0

Browse files
authored
Merge pull request #100184 from adamtuck-msft/patch-1
Update how-to-deploy-service-fabric-application-system-assigned-manag…
2 parents 567f195 + 2b4df0f commit f10b7c0

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ ms.date: 07/11/2022
1717
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.
1818

1919
> [!NOTE]
20-
> Deployment of Service Fabric applications with managed identities are supported starting with API version `"2019-06-01-preview"`. You can also use the same API version for application type, application type version and service resources. The minimum supported Service Fabric runtime is 6.5 CU2. In additoin, the build / package environment should also have the SF .Net SDK at CU2 or higher
20+
> Deployment of Service Fabric applications with managed identities are supported starting with API version `"2019-06-01-preview"`. You can also use the same API version for application type, application type version and service resources. The minimum supported Service Fabric runtime is 6.5 CU2. In addition, the build / package environment should also have the SF .Net SDK at CU2 or higher
2121
2222
## System-assigned managed identity
2323

0 commit comments

Comments
 (0)