Welcome to the Microsoft Q&A portal.
Based on the official Microsoft documentation and public announcements, here's the situation regarding Azure AD Pod Identity on AKS:
Yes, you should expect Azure AD Pod Identity to effectively stop working in a supported and maintained way after September 2025.
- Official End of Support: The AKS Pod Identity Managed add-on will be patched and supported through September 2025. This is a hard deadline for receiving official security updates and bug fixes.
- Deprecation and Archival: The underlying open-source
aad-pod-identity
project was already deprecated in October 2022 deprecation notice and its GitHub repository was archived in September 2023. This means there is no further development on the project. Use Microsoft Entra pod-managed identities in Azure Kubernetes Service (Preview) - Azure Kubernetes Service | Microsoft Learn - Functionality After the Deadline: While your existing workloads might continue to function immediately after September 2025, they will be in an unsupported state. This means if you encounter any bugs, security vulnerabilities, or compatibility issues with new versions of Kubernetes or Azure, Microsoft will not provide a fix.
The "grace period" is not for continued use, but for migration. Microsoft has provided this window specifically to give customers like you time to move their workloads to the recommended, modern solution: Microsoft Entra Workload ID.
It is highly recommended that you prioritize your migration plan to be completed well before the September 2025 deadline to avoid any potential service disruptions, security risks, or the need to fix issues without official support.
Please refer : Migrate your Azure Kubernetes Service (AKS) pod to use workload identity - Azure Kubernetes Service | Microsoft Learn