Reconciliation of BPOS and NDUS AD Identifiers
With ADFS/DirSync, Office 365 will be fully managed by the NDUS AD/IdM system, so all Office 365 (BPOS) identifiers need to be in the NDUS AD/IdM system.
Local Campus Identifiers are those identifiers that start with the campus initials, [campus initials].[ID]@[campus].edu. These identifiers need to be created in the local campus OU in the NDUS AD system.
For other identifiers no in the NDUS AD system, you will need to make the account a Person Of Interest (POI) with IT Services. This will create an account for them in AD/IdM.
Other options are to:
– change the BPOS identifier to match the NDUS AD identifier. Note: When Outlook is configured, it will setup a new profile.
– working with your campus IT Security Officer, see if the the NDUS AD identifier can be changed to the preferred identifier.
For identifier with hyphens or that are greater than 20 characters:
– Submit a request to see if the preferred identifier is available in DNA, if it is to reserve it. This request should go to the NDUS IT Security Officer, Dick Jacobson.
– Set the BPOS sign in address (Username and Domain) to the NDUS AD identifier, which does not contain any hyphens and is 20 characters or less.
– Set the BPOS default e-mail address to the preferred e-mail address (identifier).
Note: Before Outlook is configure or a new identifier, you may want to export or save the Outlook local settings: signatures, layout and other customizable settings. The new identifier will create a new profile.
Overall Migration Plan
For the Office 365 migration, the only thing that needs to be done is:
– Everyone needs to change their BPOS password
– Confirm minimum software requirements
– Near the migration time, install Lync and/or the Sign On Assistant
The plan is to manage Office 365 via ADFS/DirSync, via the NDUS AD system. To do this, there are a lot of processes that need to be developed and implemented. If this can be done by the migration weekend, then ADFS/DirSync will be implemented. If not, we will use the native Office 365 management console, which is similar to the BPOS console. This decision will be made before Aug 30, so the proper documentation and training can be provided.
Calendar – Tentative Communication Dates
A draft of the e-mail message and web pages will be made available the week of Aug 6.
While the NDUS will be sending out notices, we also encourage each campus to send out notifications, post notices in newsletters, and other communication channels to get the word out.
8/20 – General message – All BPOS end-users
8/27 – Password change required – All BPOS end-users
9/4 – Password change required – Directed, have not changed yet
9/10 – Password change required – Directed, have not changed yet
9/17 – Password change required – Directed, have not changed yet
9/20 – Final notice, with post migration information – All BPOS end-users
9/24 – Migration complete, with post migration information – All BPOS end-users