momose.blogg.se

I don't see much benefit using the Business Support link above since this is not a on-prem issue and the backend product group are well aware of the problems and have acknowledge to me and others in the thread that the fix is being worked on.

These are the three cases I had opened with M365/Office 365 Support. Finally now they realise that it's a problem with the Graph API and are awaiting updates from the backend product group - so most definitely the more cases logged on the issue will hopefully bring more attention to the problem for a fast fix. We are a Silver Partner and had a very difficult time trying to convince the Partner support team who are also the same people running M365 support that this was not a on-premise server issue. O365 will likely not make any change that will allow the sync to work, and it will be on the Server 2016 to fix where the password sync tool attempts to connect with a patch or update. Unfortunately many businesses likely used 2016 because 2019 did not have the Access Anywhere function many have leaned on since SBS 2003/2008. Since Essentials 2016 was in that awkward place between SBS 2011 and Essentials 2019 of forcing transition into the cloud and removal of On-Prem services, it is likely this small segment did not seem important. I suspect that O365 changed the Graph segment of Azure AD and failed to coordinate with the Server Essentials 2016 team.

They also said it was basically the On-Prem teams problem and not O365. They said it was a known issue, and gave me a link to this post (which I had already found and sent the link with my initial O365 ticket request. They said I will need to open a ticket with the On-Prem support team, and that it was paid support.

Just talked with an O365 support rep on this issue.