@Dashrender said in Managing Distribution Groups in an Exchange Hybrid Environment:

@EddieJennings said in Managing Distribution Groups in an Exchange Hybrid Environment:

I ought to have clarified. DUO MFA comes into play with Outlook for our mailboxes that are in Exchange Online. On-prem mailboxes (the few we have left aren't subject to DUO).

Are those that are left on prem - are they actual users? If so, I'm curious why they can't be migrated?

Eventually all users will be migrated, so, yes, we still have real users on-prem.

This is outside the scope of the original question / scenario, but I've learned a good bit during this process with much of that learning validating a few things I already knew, such as the value of taking the necessary time to plan, and prep the environment for migration (removing unnecessary objects, etc.).

So far the rebuild appears to be still working. It ran all night. No complaints yet.

As above what they are are saying is that using Hybrid AD is fine with a domain name that is not the same as long as you add the UPN in Active Directory Domain Trusts and then you adjust all the users in the domain to match that domain either manually or scripted.
https://docs.microsoft.com/en-us/office365/enterprise/prepare-a-non-routable-domain-for-directory-synchronization

My only concern with this is that you might not need to sync AD but if you are already setup then it is kinda hard to revert.

I have not dealt with this much, however I have seen sharing groups get their members removed completely.

I was only looking at exchange online plan 1, but possibly also Azure AD functionality since I was getting into O365 by a toe.

@michiganbb So you thought that necro-posting and whining about a 3yo post would be useful? Give it a try and see if that fixes your issue. You would have to do this anyway. Even if something works for one, doesn't mean there's a guarantee it works for you,. Backup the PC and try the changes. If they don't work...move on to something else.

There was NO resolution here. Client was one of those who was difficult getting payment from so we terminated the relationship before we did anything else.

Azure AD's Use of SAML Protocol

@scottalanmiller said in SSO with Azure & On-Prem AD:

Have not tried that. Would be awesome to see working.

I'd love to have had more time to play with it than being given the go-ahead at 3 pm on Friday to have it done by Tuesday morning at 8 am. After cleaning up the Server 2016 that was an attempt @ ADFS by the on-site that assumed A records are auto-created because Azure is integrated and AD, AD Connect, IIS, and SQL would be "OK" on the same server.