Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

azuread_conditional_access_policy - support for Workload Identities #1138

Closed
bubbletroubles opened this issue Jul 5, 2023 · 2 comments
Closed

Comments

@bubbletroubles
Copy link
Contributor

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritise this request
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritise the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

Conditional Access for Workload Identities are now GA by Microsoft. The Azure AD Terraform Provider does not support configuring workload identities yet.

New or Affected Resource(s)

Unsure if this should be added to azuread_conditional_access_policy or if its unique enough for its own resource

Potential Terraform Configuration

TBC

References

https://techcommunity.microsoft.com/t5/microsoft-entra-azure-ad-blog/microsoft-entra-workload-identities-now-generally-available/ba-p/3402815

https://learn.microsoft.com/en-us/azure/active-directory/conditional-access/workload-identity

  • #0000
@manicminer
Copy link
Contributor

Resolved with #1047

@github-actions
Copy link

This functionality has been released in v2.40.0 of the Terraform Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 13, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants