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 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

If all you do is assign an Office 365 license, the user will only have the e-mail address of . You have to claim the user in order to give them an account in the domain that you manage.  So, if the user should have an address, you'll need to choose that domain in box that is labeled '365 Primary Email Address' and then click 'Update 365 Primary Address.'  From this page you can also set the user's Display Name and assign aliases as well as setup the SendAs Delegation (more on this below the graphic).

Aliases - Aliases in Office 365 are alternate addresses that will deliver to the user's mailbox.  For example, if user could have an alias of .  However, be careful when assigning these aliases because, at present, users cannot send mail as an alias from Outlook Web Access (OWA), from Outlook or from a mobile device connected via the Microsoft Connector.  New users should either send mail as  or setup a vanity address and assign it as their SendAs Delegation Address.  The only way to send e-mail using an alias is to use an alternate e-mail client configured for IMAP and SMTP.

SendAs Delegation - Rutgers allows for users to setup three vanity address in the 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 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 aliases to point to the user's @connect address.

Next Steps for the User

After the account has been claimed it will, again, take about 15 minutes for that change to sync to AAD.  After that sync has taken place the user should be able to login.  The only exception will be a user who has not changed their password since January 15, 2016.  If their NetID password wasn't changed since that date, the password does not exist in AAD.  The user will need to change their NetID password and, once it has sync'ed to AAD*, they should be able to login using their  username.

Users can manage their own SendAs address at

* 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.