Forum Discussion
Cloud PBX + Cloud Connector Edition resulting in calls not in service
I ran through these steps, and was also able to set the Immutable to $null using Set-MSOLUser -UserPrincipalName <name> -ImmubatbleID "$null"
Unfortunately, I still seem to have the issue (and yes, directory sync is showing false)... CAlls are going "fast busy" and the snooper logs still show "User not found"
Also tried it with another account and the same issue persists.
As another point of reference, I created a brand new account in the Office365 cloud and assigned it an E5 license, then enabled enterprise voice and hosted voicemail, assigned it an onprem PSTN number Finally, attempted to login as that user and make phone calls. Exact same errors - the snooper logs show all numbers as coming back with the ms diagnostics 1003 " User not found"
Fistly, I would like to accentuate that I am trying to resolve your issue voluntarily based on best of my understanding with absolutely no guarantee or warranty fitting to your issue/environment.
As a community contributor, I strongly recommend you open a ticket with Microsoft and/or engage a professoinal assistance to resolve your issue as it seems that "a live troubleshooting" is needed.
Having said that if you are still willing to try on your own, here are some steps,Based on my best understanding of your issue, you would have to re-enable your AADSync.
A good example is here:
Ref: http://www.wapshere.com/missmiis/breaking-the-aadconnect-link-an-alumni-example.
In short,
- You have to put a user into an OU, for example, "USEROU"
- Launch AADConnect, choose NOT to sync "USEROU" in the sync scope options
- Run AADSync
- Cloud will (soft) delete the user in the AD
- Then you try to restore using the following commands
Restore-MsolUser -UserPrincipalName $user.UserPrincipalName -AutoReconcileProxyConflicts -NewUserPrincipalName $user.UserPrincipalName
- Assign an appropriate license to the user
- The user will become a pure Cloud user.
- Once it's confirmed working, please do the same for all users by putting all uesrs in a new OU.
So its been several days and the problem is still exactly the same.
- I suggest you wait for 1-2 days.
Microsoft office cloud is still seeing all ur users as "users synced from on-Prem ad" as I pointed out as the root cause of the issue .
Meanwhile, u may open a ticket with Microsoft as there may be a case whereby Microsoft has to make changes in their backend system.
Since the root cause and what's to be done to fix is known, the rest is pretty much hands-on.
