Office 365 Usercredentials are cached
We migrated our data from one tenant to another and a lot of the local user profiles still caches the old tenant data. We found that out because they had a lot of problems with the Teams client in connection with Outlook. Sent out Teams meeting invitations but weren't able to join the meetings... And we also figured out that if we are using this command: dsregcmd /status and the "Work Account 1" is still using the old Tenant (Tenant name, Tenant ID). So the user has to disconnect here manually. But is there a way to do it via Powershell? Or is there any other way to do it remotely for all users? Thanks in advance
Cutover migration with already setup Azure AD and SSO
Hi All, We are looking at doing a cutover migration with our current Exchange 2010 DAG setup to exchange online. We have about 112 users to move so going with the cutover. We're going that way also to remove the ned of having an onsite exchange presents. Only thing that's I've been reading about is that you need to disable DirSync to perform the cutover migration. My question(s) are 1. Will disabling DirSync (which will move all users into the deleted users) stop SSO access to our over products we use day in and day out. 2. Does having an already synced Azure AD impact on the migration, IE will it duplicate users/mailboxes 3. Does having no exchange presences onsite with DirSync enabled (After migration) cause issues? we have no plan on moving back to onsite. We do plan on keeping users onsite and in azure with the Sync Thanks a bunch, I cant find any documentation that covers our specific scenario
Add domains in one tenant OR create individual tenants, that is the question
Hi guys, Pretty monumental decision needs to be made sooner rather than later, and I understand there are pros and cons to each. There are a total of 5 companies that are all part of the same family of companies, with one of the 5 companies being the mothership/holding company. To facilitate collaboration (Teams) I've initially thought that creating everyone inside of one tenant is the better answer. However, if these companies, as they grow, institute their own policies for things, would it make more sense to break them out now into their own tenant? I'm also thinking of branding situations in Azure AD and internal company communications may be better achieved with individual tenants, but would collaboration and granular permissions suffer as a result? Want to make this transition from G Suite to Office 365 a great move; one that everyone is glad happened and not one that is regretted. Any advice, best practices, etc. are welcome and appreciated. Thank you friends!
