Forum Discussion
Cloud PBX + Cloud Connector Edition resulting in calls not in service
Here's the output of the user I'm testing with. Happens to be my account..
ExtensionData : System.Runtime.Serialization.ExtensionDataObject
AlternateEmailAddresses : {ALTEMAIL}
AlternateMobilePhones : {}
AlternativeSecurityIds : {}
BlockCredential : False
City : CITY
CloudExchangeRecipientDisplayType : 1073741824
Country : United States
Department :
DirSyncProvisioningErrors : {}
DisplayName : DISPLAY NAME
Errors :
Fax :
FirstName : FIRST NAME
ImmutableId : i9Zr9uuYH0ugtQvi2vE3WQ==
IndirectLicenseErrors : {}
IsBlackberryUser : False
IsLicensed : True
LastDirSyncTime :
LastName : LAST NAME
LastPasswordChangeTimestamp : 6/4/2017 8:55:27 PM
LicenseReconciliationNeeded : False
Licenses : {rfischmanrehobothambulance:ENTERPRISEPREMIUM, rfischmanrehobothambulance:EMS}
LiveId : 10037FFEA1CE11F9
MSExchRecipientTypeDetails :
MobilePhone : MOBILEPHONE
ObjectId : 92e1bd1e-bbb7-453f-bea6-a1dec1dad6b6
Office :
OverallProvisioningStatus : PendingInput
PasswordNeverExpires : XXXXXXX
PasswordResetNotRequiredDuringActivate :
PhoneNumber : OFFICE PHONE
PortalSettings : PortalSettings
PostalCode : ZIP
PreferredDataLocation :
PreferredLanguage : en-US
ProxyAddresses : {SMTP:EMAIL ADDRESS}
ReleaseTrack :
ServiceInformation : {}
SignInName : SIGNIN NAME
SoftDeletionTimestamp :
State : STATE
StreetAddress : STREET ADDRESS
StrongAuthenticationMethods : {Microsoft.Online.Administration.StrongAuthenticationMethod,
Microsoft.Online.Administration.StrongAuthenticationMethod}
StrongAuthenticationPhoneAppDetails : {}
StrongAuthenticationProofupTime :
StrongAuthenticationRequirements : {}
StrongAuthenticationUserDetails : Microsoft.Online.Administration.StrongAuthenticationUserDetails
StrongPasswordRequired : True
StsRefreshTokensValidFrom : 6/4/2017 8:55:27 PM
Title :
UsageLocation : US
UserLandingPageIdentifierForO365Shell :
UserPrincipalName : USERPRINCIAPLNAME
UserThemeIdentifierForO365Shell :
UserType : Member
ValidationStatus : Healthy
WhenCreated : 5/28/2017 1:34:44 PM
And I noticed provisoning status shows pending input. Here's the status of the assigned products:
ServicePlan ProvisioningStatus ----------- ------------------ FORMS_PLAN_E5 Success STREAM_O365_E5 Success THREAT_INTELLIGENCE Success Deskless Success FLOW_O365_P3 Success POWERAPPS_O365_P3 Success TEAMS1 Success ADALLOM_S_O365 PendingInput EQUIVIO_ANALYTICS Success LOCKBOX_ENTERPRISE Success EXCHANGE_ANALYTICS Success SWAY Success ATP_ENTERPRISE PendingProvisioning MCOEV Success MCOMEETADV Success BI_AZURE_P2 Success INTUNE_O365 PendingActivation PROJECTWORKMANAGEMENT Success RMS_S_ENTERPRISE Success YAMMER_ENTERPRISE Success OFFICESUBSCRIPTION Success MCOSTANDARD Success EXCHANGE_S_ENTERPRISE Success SHAREPOINTENTERPRISE Success SHAREPOINTWAC Success
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. 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"
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.
SOLUTION
You want to manage objects in Office 365, Azure, or Intune and you no longer want to use directory synchronization.- Install the Azure Active Directory Module for Windows PowerShell. For more info, go to the following Microsoft website: http://aka.ms/aadposh
- Connect to Azure AD by using Windows PowerShell. For more info about how to do this, go to the following Microsoft website:http://technet.microsoft.com/library/jj151815.aspx#bkmk_connect
- Disable directory synchronization. To do this, type the following cmdlet, and then press Enter:
Set-MsolDirSyncEnabled –EnableDirSync $false
- Check that directory synchronization was fully disabled by using the Windows PowerShell. To do this, run the following cmdlet periodically:This cmdlet will return True or False. Continue to run this cmdlet periodically until it returns False, and then go to the next step.
(Get-MSOLCompanyInformation).DirectorySynchronizationEnabled
Note It may take 72 hours for deactivation to be completed. The time depends on the number of objects that are in your cloud service subscription account.
- Install the Azure Active Directory Module for Windows PowerShell. For more info, go to the following Microsoft website:
It's confirmed that Microsoft Office365 portal is still seeing all your users as "Synced with on-premise Active Directory"
Root Cause: Microsoft Office365 portal is still seeing all your users as "Synced with on-premise Active Directory" after you migrated your AD users to Office365.
This has been a long strech of finding out what's going on. Finally, I managed to pin down the "Root Cause of the Issue" in conclusive manner. :D
As you can see, the ImmutableID is still showing GUID which means Office365 portal is still seeing all your users as "Synced with on-premise Active Directory"
ImmutableId : i9Zr9uuYH0ugtQvi2vE3WQ==
If it is a pure Cloud user, you shold see "blank" in ImmutableID paramter.
Let me see how to fix/workaround over it.