Skip to content

Commit 6051938

Browse files
authored
Merge pull request #51390 from jagilber/patch-2
Update configure-existing-cluster-enable-managed-identity-token-service.md
2 parents 2d79103 + 1f7bc9d commit 6051938

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/service-fabric/configure-existing-cluster-enable-managed-identity-token-service.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -35,7 +35,7 @@ To enable the Managed Identity Token Service in an existing cluster, you will ne
3535
]
3636
```
3737

38-
In order for the changes to take effect, you will also need to change the upgrade policy to specify a forceful restart of the Service Fabric runtime on each node as the upgrade progresses through the cluster. This restart ensures that the newly enabled system service is started and running on each node. In the snippet below, `forceRestart` is the essential setting; use your existing values for the remainder of the settings.
38+
In order for the changes to take effect, you will also need to change the upgrade policy to specify a forceful restart of the Service Fabric runtime on each node as the upgrade progresses through the cluster. This restart ensures that the newly enabled system service is started and running on each node. In the snippet below, `forceRestart` is the essential setting to enable restart. For the remaining parameters, use values described below or use existing custom values already specified for the cluster resource. Custom settings for Fabric Upgrade Policy ('upgradeDescription') can be viewed from Azure Portal by selecting 'Fabric Upgrades' option on the Service Fabric resource or resources.azure.com. Default options for the upgrade policy ('upgradeDescription') are not viewable from powershell or resources.azure.com. See [ClusterUpgradePolicy](https://docs.microsoft.com/en-us/dotnet/api/microsoft.azure.management.servicefabric.models.clusterupgradepolicy?view=azure-dotnet) for additional information.
3939

4040
```json
4141
"upgradeDescription": {
@@ -67,4 +67,4 @@ If the deployment fails with the following message, it means the cluster is not
6767
* [Deploy an Azure Service Fabric application with a system-assigned managed identity](./how-to-deploy-service-fabric-application-system-assigned-managed-identity.md)
6868
* [Deploy an Azure Service Fabric application with a user-assigned managed identity](./how-to-deploy-service-fabric-application-user-assigned-managed-identity.md)
6969
* [Leverage the managed identity of a Service Fabric application from service code](./how-to-managed-identity-service-fabric-app-code.md)
70-
* [Grant an Azure Service Fabric application access to other Azure resources](./how-to-grant-access-other-resources.md)
70+
* [Grant an Azure Service Fabric application access to other Azure resources](./how-to-grant-access-other-resources.md)

0 commit comments

Comments
 (0)