Hi Cursor Team,
First off, thanks for the excellent work on Cursor! I’ve been enjoying using it for my workflow and find the features and ease of integration very helpful.
I’m reaching out to request support for Azure OpenAI Entra ID (AAD) authentication in addition to the existing key-based authentication method. While the key-based approach is functional, Entra ID authentication would provide a few key benefits for users, especially those with compliance requirements or security needs.
Why Entra ID Support?
- Increased Security: Unlike key-based authentication, Entra ID provides robust security controls and enables finer-grained access management.
- Reduced Key Rotation: With Entra ID, I would no longer need to rotate keys periodically, which is both more secure and reduces administrative overhead.
- Compliance Requirements: Some of us need to comply with specific industry regulations or internal policies that mandate identity-based authentication rather than key-based access.
Potential Benefits of Implementing This Feature
- Better user experience for organizations already leveraging Entra ID for authentication across services.
- Increased adoption among enterprise users who require identity-based access controls for their security and compliance policies.
- Simplified authentication management for admins who prefer managing access through Entra ID roles and permissions.
Proposed Implementation
Allow users to toggle between key-based and Entra ID authentication in settings. This way, existing key-based users can continue using their current setup, and those of us looking to implement Entra ID can have that option available.
Thank you for considering this feature request. Please let us know if this is something that could be added to your roadmap, and if so, a rough timeline would be appreciated. I believe this feature would provide value to many users looking for enhanced security and compliance support.
Best regards,
Shuai