Skip to content

Commit 456f7f4

Browse files
committed
fixed casing of proper noun
1 parent d6489ea commit 456f7f4

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/aks/workload-identity-migrate-from-pod-identity.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ This section explains the migration options available depending on what version
2323
For either scenario, you need to have the federated trust set up before you update your application to use the workload identity. The following are the minimum steps required:
2424

2525
- [Create a managed identity](#create-a-managed-identity) credential.
26-
- Associate the managed identity with the kubernetes service account already used for the pod-manged identity or [create a new kubernetes service account](#create-kubernetes-service-account) and then associate it with the managed identity.
26+
- Associate the managed identity with the kubernetes service account already used for the pod-manged identity or [create a new Kubernetes service account](#create-kubernetes-service-account) and then associate it with the managed identity.
2727
- [Establish a federated trust relationship](#establish-federated-identity-credential-trust) between the managed identity and Azure AD.
2828

2929
### Migrate from latest version

0 commit comments

Comments
 (0)