Search the Community

We’re currently reviewing our staff leavers process. One of the suggestions that leadership has come up with is, when a staff member leaves, could we move their email address (note: NOT their mailbox) to another mailbox which has an autoreply set on it telling people this person no longer works for us? Our accounts are on-premise AD accounts with mailboxes in Exchange Online, synced via Azure AD Connect, so this doesn’t seem as straightforward as I might otherwise have thought. Does anyone know how long we have to wait between removing the email address and proxyAddress from the source AD account, before it can be added to the proxyAddresses in the destination AD account? Or, is there a different way we should be thinking about this?

We joined up with Locker Connect this last Summer to get ourselves on the automatic account creation bandwagon. We chose them over Salamander as we liked the look of what we saw. However, I'm not getting the functionality that I was expecting. Now I'll say right now, I'm not saying the software doesn't work, but I do think that somewhere along the way our configuration hasn't been set how we want it. We use Bromcom as our MIS (don't get me started about that right now) and Microsoft 365 as our email system. We are also using Azure AD Connect (or Entra) to link up our onsite AD with Azure so we can enable single sign-on. Accounts are creating in both AD and 365, and they are adding to correct groups in AD... but not in 365? Even though the named groups are proper "Microsoft 365 Groups". Locker say that our 365 accounts are getting created by Azure Connect rather than Locker, and so they are having to handle accounts after the fact. But because of this, they can't handle group management? Does that sound correct? Does anybody else out there use Locker with 365 and have a SSO system? Do you have any issues with group allocation? Are you making use of Azure/Entra Connect? Basically, what is your working setup that we seem to not have?! Driving me potty as I'm sure we can achieve what we want without having to switch to Salamander, but I just can't get my head around it. And right now it's hindering our next step in our big project of shifting a lot of data into SharePoint and Teams.

Looking to remove Azure AD Connect away from a hybrid AD and Microsoft 365 environment. Currently users are synced from local AD. We want to create users in AD and 365 separately (I know(!), but part of a long term plan). Currently users made & configured in AD, synced to 365 and license/mailbox applied. What happens to existing (synced) users? Obviously passwords etc will be separate for AD & 365, but any issues come to mind when I disable synchronisation? Specifically we have edited the proxyAddresses attribute in local AD pointing to the 365 username/email address.