A container has more than one identity boundary on its way to useful work. The kubelet needs permission to retrieve an image. The application inside the Pod may need a different permission to read storage or call a protected service. Fenwick Design can start its image but still receives a storage denial when the application runs.
Use the observed failure stage to choose which identity to inspect. Entra workload federation can connect a Kubernetes service-account flow to a scoped Azure identity, but a local identity object and a role record do not implement that token exchange. These tasks create local access intent and examine the distinctions. No real tokens, federation, registry authentication or Azure authorization is executed. The worked example names the roles of the identities rather than suggesting that one broad node grant is a complete application-security design.
Use the failure stage to inspect the right identity.