In order to connect UMRA to your Office 365 tenant, and begin managing users and groups, you will need to install/configure several prerequisites.
- Create an administrative service account inside of Office 365. Make note of its username and password, as you will need it inside of UMRA.
- We recommend ensuring that the account's password does not expire.
- Microsoft Online Services Sign-In Assistant
- Windows Azure AD Module for Windows PowerShell
Once the prerequisites are installed, we recommend verifying connectivity to Office 365. This can be easily done through native PowerShell, without involving UMRA.
- Launch PowerShell
- Run the following script, supplying the administrative service account credentials when prompted:
$msolcred = get-credential
connect-msolservice -credential $msolcred
Create Your Script
Now that you can connect to Office 365's PowerShell interface, you can begin using UMRA to manage your users and groups in the cloud.
- Launch the UMRA Console from the Start Menu
- Create a new script
- In the Actions pane, expand the Powershell > Agent service session folder
- Drag a Setup PowerShell Agent service session action into your script pane
- Drag a Release PowerShell Agent service session action just underneath of it
- In the Actions pane, expand the Office 365 > General folder
- Drag a Office 365 Setup connect action into your script pane, between your Setup and Release Powershell actions
- You will need to configure the Username and Password properties of this action
Note that the values of the Office 365 Connection properties of the Office 365 actions, and the Session ID properties of the PowerShell actions do not match. This must be rectified, as all actions that take place inside of a PowerShell session must connect to the same session variable.
- Select your Setup PowerShell Agent service session action, and double click on its Session ID property
- Change the output value variable from %PowershellAgentSessionId% to %G_Office365PowerShellSession%
- Do the same for the Release Powershell Agent service session action
Save and run your script, and troubleshoot any errors that are reported (e.g., access denied, bad credentials, etc.). Once you can run your script with no errors, you are ready to add more actions, such as pulling data from an HR system, creating users, groups, etc.