Duplicate post... sorry. Can't remove it so added more text to clarify the problem.....

Hi all, another day another strange issue. I have logged a call with MS but thought I would post here in case anyone has seen this before.

Added in about 6 users this morning to our AD group which AD Connect picks up to sync to Azure, and CM picks up to add the users to the user collection that is attached to the intune sub. and licenses them.

AD Sync worked and users appear in Intune, collection got updated in CM everything was good, but the users were getting user account not recognised. We have had this when users are not licensed. Looking through the cloudusersync.log I found these errors for the users concerned.

WARNING: Iterating over results of the AddAddLicensedUsers service call: One of the UserLicense entity results returned was null corresponding to upn <users UPN>

Added in a new test user shortly afterwards and this was licensed in the log as expected, also added an existing user and this too was licensed.

We manually licensed the users in the Intune console and this allowed us to continue enrollment but I need to get to the bottom of this.

Anyone seen this before? Any tips of progressing the troubleshooting?

• Edited by jmf123 Tuesday, August 25, 2015 6:42 AM

Hi all, another day another strange issue. I have logged a call with MS but thought I would post here in case anyone has seen this before.

Added in about 6 users this morning to our AD group which AD Connect picks up to sync to Azure, and CM picks up to add the users to the user collection that is attached to the intune sub. and licenses them.

AD Sync worked and users appear in Intune, collection got updated in CM everything was good, but the users were getting user account not recognised. We have had this when users are not licensed. Looking through the cloudusersync.log I found these errors for the users concerned.

WARNING: Iterating over results of the AddAddLicensedUsers service call: One of the UserLicense entity results returned was null corresponding to upn <users UPN>

Added in a new test user shortly afterwards and this was licensed in the log as expected, also added an existing user and this too was licensed.

We manually licensed the users in the Intune console and this allowed us to continue enrollment but I need to get to the bottom of this.

Anyone seen this before? Any tips of progressing the troubleshooting?

• Merged by Bennie ChenMicrosoft employee, Moderator Thursday, August 27, 2015 11:19 AM duplicate

Duplicate post of https://social.technet.microsoft.com/Forums/en-US/a0cd040c-a0bf-43bb-8501-1ac2330459d8/issue-with-cm-2012-r2-sp1-cu1-licensing-users?forum=microsoftintuneprod

Thanks Garth, I must have accidentally submitted before I had finished writing it :-)

Hi,

What were you doing when you got this warning? You need to provide more information about your context.

Hi Sue_ran

Please see the other post, this one I accidentally submitted before I had finished... *or even started writing it. Thanks

https://social.technet.microsoft.com/Forums/en-US/a0cd040c-a0bf-43bb-8501-1ac2330459d8/issue-with-cm-2012-r2-sp1-cu1-licensing-users?forum=microsoftintuneprod

Jody

Update: Looking like it was a brief service issue on the Intune side of things at the moment and not to do with our local Infrastructure.

• Proposed as answer by Garth JonesMVP, Moderator Tuesday, August 25, 2015 4:59 PM
• Marked as answer by Bennie ChenMicrosoft employee, Moderator Monday, September 07, 2015 2:05 AM

Update: Looking like it was a brief service issue on the Intune side of things at the moment and not to do with our local Infrastructure.

• Proposed as answer by Bennie ChenMicrosoft employee, Moderator Thursday, August 27, 2015 9:18 AM

Hi All

I had this issue occur again and had a moment to delve in deeper, so I did some further testing. In my testing I have found that this error occurs when the user is picked up in the CM collection and the cloudusersync runs before the user is synchronised to AAD.

Overnight once the user is synchronised to AAD cloudusersync does pick up the user and license it again, but I assume it only does this when it runs a full sync overnight but does not pick up the user with the incremental syncs during the day. This occurred for me because in the testing I was using the same group to scope the AAD sync as I was using for CM to build the collection. Despite a manual sync to AAD it was pot luck which one would run/finish first.  

Implication for a design is that the users must be synchronised before cloudusersync runs. If scoped on an OU then generally this would happen as all users would already be there.

I am trying to find out if there is a manual way to force a full cloudusersync in the event this were to occur again.