Provisioning New Users in Rutgers Connect
When a new user is given a NetID, an account is automatically created for them in Rutgers Active Directory (RAD). Once that account is created, the DirSync software creates the account in Azure Active Directory (AAD). This is the directory service that Rutgers Connect (RC) uses to authenticate users.
At this point the user exists in the @connect.rutgers.edu domain in RC but they do not have an Office 365 license assigned and they have not be "claimed" by a department. Under normal circumstances, the user will need to be licensed and claimed by a department.
Licensing the User
Licensing the user is required before their account will work. This can be done by searching for the user by NetID in the Connect Admin Tool (CAT). The user will appear with a red box because the account is not yet active. Click the button to 'Assign Office 365 License' and a license will be assigned. This change will not be immediate. It usually takes no more than 15 minutes for this change to sync into AAD but, depending on load, it's possible that it will take longer. Once this has been completed, you can move on to the next step.
Claiming the User
SendAs Delegation - Rutgers allows for users to setup three vanity address in the @rutgers.edu domain. Users can choose one of these addresses as their SendAs delegation address so they can send mail using this address in Rutgers Connect. This address will work in Outlook and OWA (but in OWA they will have to choose it as an alternate address each time the send an e-mail). This address can also be used with an email client configured with IMAP and SMTP.
Setting up @rutgers.edu forwarding
Currently, when a new account is created, the old process of pointing that account at RCI by default is still in place. There is now a button on the user screen in Rutgers Connect that allows you to change their @rutgers.edu aliases to point to the user's @connect address.
Next Steps for the User
Users can manage their own SendAs address at http://netid.rutgers.edu.
* The first password sync is the only time a password change will take 15 minutes to take effect. This is because accounts without a password are created as disabled. While the password itself syncs almost instantly, the enabling of the account is part of the standard sync that occurs about every 15 minutes. Once the account has been enabled, password syncs will be virtually instananteous.