Migration from Microsoft Active Directory to Azure AD
What does this mean in simple terms? We are in migration-mode towards an overall better system for the management of user accounts, groups and devices.
Active Directory (Alliant’s legacy system)
Azure AD (Alliant’s emerging system)
You have already been part of our initial migration efforts through the implementation of multi-factor authentication (MFA) and reconfiguration of your computer to join Azure AD and Mobile Device Management (MDM).
Our next steps will focus on migrating Email distribution lists from AD to Azure AD. The first of these moves will be for the Student groups by Campus and by Program.
The distribution list migration should not affect current rights for who can send to a group(s). But, you need to be aware of cached name entries as these will NOT work. (Even though the name appears the same as the new Azure group name)
Active Directory (Alliant’s legacy system)
- dated, on-premise based technology
- difficult to keep current for the protection from malicious activity
- minimal tools to account for status of university computers
- no integrated ability to support devices unless they are directly connected to the Alliant campus network
- device status and reports must be manually performed
Azure AD (Alliant’s emerging system)
- modern, enterprise level cloud-based technology
- extremely secure with variable protection controls
- tools to deploy updates to and manage computers in bulk
- built-in tool to provide “remote” support to university computers via the Internet
- device status and reports are available via dashboard or simple query
You have already been part of our initial migration efforts through the implementation of multi-factor authentication (MFA) and reconfiguration of your computer to join Azure AD and Mobile Device Management (MDM).
Our next steps will focus on migrating Email distribution lists from AD to Azure AD. The first of these moves will be for the Student groups by Campus and by Program.
- Examples are; Alliant Students All, Alliant Students Fresno, Alliant Students Los Angeles CSPP, Alliant Students CSOE, etc.
The distribution list migration should not affect current rights for who can send to a group(s). But, you need to be aware of cached name entries as these will NOT work. (Even though the name appears the same as the new Azure group name)
- If you regularly message a group, a cached entry option will automatically pop up when you begin to type a name in the To/CC of Bcc field.
- To avoid using an outdated cached entry, you can select the X to the right of the group name when it appears. Then use the Global Address List to select the new group designation.
- After you send a message, a new cached entry will be created and you can continue to use this.
How to delete an address from the Outlook Name Cache
Outlook Desktop Client Application:
Outlook Web App:
Outlook App for iPhone:
|
|
|
|
Outlook Student Distribution Lists
