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

Change user_type in azuread_user resource #941

Open
miltlino opened this issue Dec 2, 2022 · 1 comment
Open

Change user_type in azuread_user resource #941

miltlino opened this issue Dec 2, 2022 · 1 comment

Comments

@miltlino
Copy link

miltlino commented Dec 2, 2022

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

It should be possible to create member or guest users, both homed and invited in a given tenant.

New or Affected Resource(s)

  • azuread_user

Potential Terraform Configuration

resource "azuread_user" "example" {
  user_principal_name = "jdoe@hashicorp.com"
  display_name        = "J. Doe"
  mail_nickname       = "jdoe"
  password            = "SecretP@sswd99!"

  user_type = "guest"
}

Original message

Hi,

How can we change user_type of an azuread_user resource from Member to Guest using terraform

@manicminer
Copy link
Contributor

Hi @miltlino, this is unfortunately not currently possible, however in the next major version of the provider this will be addressed. I've updated your issue to use our provided issue template, please kindly use the templates provided when opening an issue as this helps us gather the information we need.

Additionally, if you have any usage questions please consult our community resources which are detailed in the README. Thanks!

@manicminer manicminer added this to the v3.0.0 milestone Jan 18, 2023
@manicminer manicminer removed this from the v3.0.0 milestone Sep 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants