Forum Discussion

Reuben Fischman's avatar
Reuben Fischman
Copper Contributor
Sep 28, 2017

Cloud PBX + Cloud Connector Edition resulting in calls not in service

I've got a Cloud PBX subscription with a few users enabled for testing.  We also have Cloud Connector Edition installed, and according to our Skype for Business Online admin portal, it is reporting i...
CCE
Cloud PBX
Reuben Fischman's avatar
Reuben Fischman
Copper Contributor
Oct 06, 2017

So its been several days and the problem is still exactly the same.

thet naing's avatar
thet naing
Iron Contributor
Oct 06, 2017

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,

  1. You have to put a user into an OU, for example, "USEROU"
  2. Launch AADConnect, choose NOT to sync "USEROU" in the sync scope options
  3. Run AADSync 
  4. Cloud will (soft) delete the user in the AD
    1. Then you try to restore using the following commands

    2.  

      Restore-MsolUser -UserPrincipalName $user.UserPrincipalName -AutoReconcileProxyConflicts -NewUserPrincipalName $user.UserPrincipalName

    3. Assign an appropriate license to the user  
  5. The user will become a pure Cloud user.
  6. Once it's confirmed working, please do the same for all users by putting all uesrs in a new OU.