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_invitation - Allow ALL Properties To Be Set (Department, Job Title etc) #1113

Closed
v1ferrarij opened this issue Jun 6, 2023 · 3 comments

Comments

@v1ferrarij
Copy link

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

When using azuread_invitation to invite Guest Users, it would be good if we can set all the properties we can when performing the same task using Azure Portal/Azure CLI.

For example, I want to set

First Name
Last Name
Job Title
Department
Manager

When using Terraform, however, I currently cannot do this with Terraform.

New or Affected Resource(s)

azuread_invitation

Potential Terraform Configuration

resource "azuread_invitation" "example" {
  user_email_address = "john.smith@microsoft.com"
  user_display_name  = "John Smith"
  redirect_url = "https://portal.azure.com"

  first_name = "John"
  last_name = "Smith"
  job_title = "Azure Consultant"
  department = "Consultancy"
}

References

  • N/A
@OskarKlintrot
Copy link

Is this a dup of #650?

@manicminer
Copy link
Contributor

Duplicate of #650

@manicminer manicminer marked this as a duplicate of #650 Jul 25, 2023
@manicminer manicminer closed this as not planned Won't fix, can't repro, duplicate, stale Jul 25, 2023
@manicminer
Copy link
Contributor

Thanks for raising this @v1ferrarij. We do intend to offer this functionality although the approach is likely to be that we roll some invitation functionality into the azuread_user resource rather than expanding the azuread_invitation resource.

This was already raised as a feature request in #650, so I've gone ahead and closed this as a duplicate, but please subscribe to #650 for updates on this. Thanks!

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

No branches or pull requests

3 participants