I think the point is that Microsoft is phasing out AD and Exchange by making the licensing costs prohibitively more expensive than just using their cloud identity, mail, and SaaS services.
We are still on prem for AD but that’s due to legacy software that requires it and will be that way for a while but cost will eventually have us on a cloud identity provider and it will probably be Azure
We already are on exchange online, the costs just don’t make sense to host exchange on premises unless you have a legacy reason too.
I think the point is that Microsoft is phasing out AD and Exchange by making the licensing costs prohibitively more expensive than just using their cloud identity, mail, and SaaS services.
We are still on prem for AD but that’s due to legacy software that requires it and will be that way for a while but cost will eventually have us on a cloud identity provider and it will probably be Azure
We already are on exchange online, the costs just don’t make sense to host exchange on premises unless you have a legacy reason too.
I really want to respond to your comment and go in more depth as to how my work situation is with AD groups etc etc
I just don’t want to be careless and speak more about the particular infrastructure of my company’s workflow than I need to
Suffice to say, we are continuing to move assets to a cloud hosting service. Due to our unique solution, we still require AD groups.
Funny enough, we need the AD groups for the cloud assets to run as expected. It’s a different kind of authorization on-prem