Shulou(Shulou.com)06/02 Report--

Environment description:

A long time ago, I applied for an office365 test account, did Exchange mixed deployment Demo, and synchronized the distribution groups in the local Exchange to Office365.

Status quo: all local server virtual machines are deleted, but nothing is done on the Office365, directory synchronization is always on, and the bound domain name is still the federated domain name. I need to apply for a new Office365 subscription to the mixed deployment of SFB2019, when binding the domain name fails.

Problem to be solved: you need to delete the group from the local Exchange Sync to remove the bound domain name. For removing the domain name, please refer to my article Office365 to remove the federated domain name.

First of all, let's take a look at why this domain name cannot be deleted:

Obviously, a group occupies the domain name and address, so take a look at this group information.

Because this group is from the local Sync to the cloud, students who have worked on the Office365 project all know that as long as the objects from the local Sync to the Office365 cannot be edited and deleted directly in the portal, the administrator will be prompted to operate locally and then synchronized to the Office365 through AAD.

But now the reality is that all the virtual machines that used to do Demo have been deleted, not to mention the local environment of Exchange and AAD.

At this time, we can get the ID information of this group by connecting to the Powershell of Office365 to see if we can delete it from Powershell.

First, get-msolgroup to get the group information

Remember the group's Objectid, and then use remove-msolgroup to remove the group

Remove-msolgroup-objectid XXXXX, and then use get-msolgroup to determine whether to delete the group

Finally, go to office365 admin portal to confirm that the group has been deleted.

PS, you must operate normally when you dismantle the mixed deployment. Don't kill the server directly like me, and then wait for Office365 to delete data automatically. It turns out that the Office365 backend will not delete data such as AD (my trial account was deleted by 21V email a long time ago, as shown below). As a result, it will be quite troublesome to use this domain name to test the mixed deployment of Office365 next time.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.