Microsoft Graph REST API Property netId is invalid error.

Question

Microsoft Graph REST API Property netId is invalid error.

Yoshida 21

I tried to create a new user by Microsoft Graph REST API v1.0 with below reference and then got following error.
https://learn.microsoft.com/ja-jp/graph/api/user-post-users?view=graph-rest-1.0&tabs=http
What kind of error ? Please tell me where should I check?
Are there different properties needed depending on the situation of the organization I am trying to add?
I don't understand it because netId doesn't seem to matter for adding users.

Property netId is invalid.

I used these properties.

accountEnabled : true
mail
surname
givenName
displayName
mailNickname
passwordProfile { forceChangePasswordNextSignIn: true, password: }
userPrincipalName
usageLocation

1 answer

Your answer

Answer 1

Srinivasa Rao Darna 6,846 Microsoft External Staff

Hi @Yoshida ,

Please refer to this how-to-fetch-cid-hex-format-of-user-ids.html.

PUID/NetID was removed from Graph API and there are currently no plans on resurfacing it. The recommendation for apps is to rely on TenantID and ObjectID to identify users and stop relying on PUID/Net ID.

Hope this helps.
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Yoshida 21 Reputation points

2022-10-31T03:28:45.623+00:00

Hi @Srinivasa Rao Darna

Thanks for your answers.

PUID/NetID was removed from Graph API and there are currently no plans on resurfacing it. The recommendation for apps is to rely on TenantID and ObjectID to identify users and stop relying on PUID/Net ID.

I don't use NetID in my property.

Here are the properties we are using as previously mentioned.
Nonetheless, it is strange that the NetID error is displayed.

accountEnabled : true

mail

surname

givenName

displayName

mailNickname

passwordProfile { forceChangePasswordNextSignIn: true, password: }

userPrincipalName

usageLocation
Zehui Yao_MSFT 5,881 Reputation points

2022-10-31T11:00:15.177+00:00

Hi @Yoshida , would you mind providing more details on how you get the token and how to request the endpoint?

Yoshida 21

Hi @Srinivasa Rao Darna .
I am using OAuth 2.0 to obtain an access token.
Scope is here.

offline_access, Organization.Read.All, User.ReadWrite.All, GroupMember.ReadWrite.All

Requests to the endpoint are made using Faraday as follows.

   def client  
       Faraday.new(url: "https://graph.microsoft.com/v1.0/") do |conn|  
           conn.response :json, content_type: "application/json"  
           conn.request :json  
           conn.request :authorization, "Bearer", -> { <access_token> }  
           conn.headers["Content-Type"] = "application/json"  
       end  
   end  
     
   client.post(  
             "users",  
             accountEnabled: true,  
             mail: <mail>,  
             surname: <surname>,  
             givenName: <given_name>,  
             displayName: <display_name>,  
             mailNickname: <mail_nickname>,  
             passwordProfile: {  
               forceChangePasswordNextSignIn: true,  
               password: <password>,  
             },  
             userPrincipalName: <user_principal_name>,  
             usageLocation: <usage_location>,  
           )

While some clients are able to create users without problems, there are also clients where netId errors appear.

Zehui Yao_MSFT 5,881 Reputation points

2022-11-01T10:28:32.563+00:00

Hi @Yoshida , please check if there is any user information that does not comply with the specification.
Keller, David J 5 Reputation points

2023-02-17T13:46:04.53+00:00

Is there any update on this issue? It seems to be intermittent, but we definitely see it about once a week in our nightly regression runs. Note that we are not setting any property called netID, nor is this something available in the .NET Graph SDK, so we have no idea where this is coming from or how to prevent it from happening.
Pak-Hun Chan 20 Reputation points

2023-04-11T18:45:33.9433333+00:00

I came across this exact same problem. My POST API request to create an AAD account gave the following error even though I didn't include a netId field.

Property netId is invalid.

It turns out that the issue was because I was trying to create an account using a userPrincipalName that already existed in my tenant. I haven't come across that issue since fixing the userPrincipalName field. AAD really needs to update their APIs' error messages.
Stephen Johnson 0 Reputation points

2024-01-04T10:42:59.4433333+00:00

@Pak-Hun Chan Thank you for posting this, this was indeed my issue as well. changed my script to check for pre-existing UPN's and now its working again.

Share via

Microsoft Graph REST API Property netId is invalid error.

1 answer

Your answer