> Automation > Running Automation Policies with Office 365 Automation Objects

Running Automation Policies with Office 365 Objects

Office 365 Automation Objects cannot interface with devices where an Agent has been installed. For other types of Automation Manager Objects, the Policies that use them are run by the Agent installed on the executing device. For Automation Policies that include Office 365 Automation Objects, however, the new SaaS Device class has been created which allows you to use these types of Automation Objects.

SaaS Devices

SaaS (Software as a Service) functionality has been enhanced by Automation Manager 1.6 with the introduction of the SaaS Device class to MSP N-central. This device class is used as the target for Automation Policies that include Office 365 Automation Objects.

The SAAS Device is used to store the credentials used to access Office 365. You should create an SAAS Device for every Customer or Site for which you need to manage Office 365 elements.

An SaaS Device cannot be configured at the Service Organization level to affect multiple Customers or Sites.

Asset Variables

Asset Variables are used when running Automation Manager Policies that include Wake On LAN, SSH, Telnet, or Office 365 objects and include:

Network Address Passes into an Automation Policy the IP or DNS hostname identified in the Network Address field of the Properties tab of a device.
MAC Address Passes into an Automation Policy the MAC address of the Network Adapter configured with the IP or DNS hostname identified in the Network Address field of the Properties tab of a device.
Device Credentials Username Passes into an Automation Policy the User Name identified in the User Name field of the Properties tab of a device.
Device Credentials Password Passes into an Automation Policy the password that is identified in the Password field of the Properties tab of a device.

Office 365 Policies

To run Automation Policies that include Office 365 Automation Objects, you will need to perform the following:

  • Create an SaaS Device in MSP N-central
  • Review Software Requirements for the Executing Device
  • Install the Windows Azure Active Directory Module on the Executing Device
  • Link the Credentials of the SAAS Device to the Automation Policy

Create an SaaS Device in MSP N-central

This procedure can only be done at the Customer or Site-level.

  1. Click Actions > Add/Import Devices.
  2. Under Manually Create a Device that Represents a SaaS Solution, click Add Device.
  3. Enter a descriptive Name to identify the device.
  4. Select the Service Vendor to be used by the device.
  5. Configure the remaining properties of the device in the Add Device screen. For more information on specific properties, refer to Device Details View. For more information on specific properties, refer to "Devices" in the MSP N-central online help.
  6. Click Save.

Review Software Requirements for the Executing Device

The executing device is a Windows computer at the Customer or Site that will be used to run Automation Policies that access Office 365.

The following information is derived from the Microsoft Technet article: "Manage Windows Azure AD using Windows PowerShell". Please refer to the original Microsoft documentation for the most current requirements and instructions related to Microsoft Windows PowerShell.

Before a device can be used to run Automation Policies that include Office 365 Automation Objects, ensure that it meets the following requirements:

Operating System Windows 7, Windows 8, Windows Server 2008 R2, or Windows Server 2012
Microsoft .NET Framework Microsoft .NET Framework 3.51
Updates Verify that all updates required by the Microsoft cloud services to which you have subscribed have been installed. For example, some cloud service features may not work properly without the appropriate versions of operating systems, web browsers, and software.
Microsoft Online Services Sign-in Assistant Install the appropriate version of the Microsoft Online Services Sign-in Assistant for the device's operating system from the Microsoft Download Center. For more information, refer to the Microsoft Online Services Sign-In Assistant for IT Professionals RTW.

Install the Windows Azure Active Directory Module on the Executing Device

The following information is derived from the Microsoft Technet article: "Manage Windows Azure AD using Windows PowerShell". Please refer to the original Microsoft documentation for the most current requirements and instructions related to Microsoft Windows PowerShell.

Depending on the operating system of the executing device, you must install the appropriate version of the Windows Azure AD Module for Windows PowerShell.

  1. Click on the Microsoft Download Center link to download the appropriate version of the Windows Azure AD Module for Windows PowerShell from one of the following:
  2. Follow the instructions of the installation software to install the module on the device.

Once the module has been installed, the list of installed software in MSP N-central should be similar to the following:

Link the Credentials of the SAAS Device to the Automation Policy

  1. Click Views > All Devices.
  2. Click the SaaS Devices tab.
  3. Select the check box next to the device (or devices) that will be the target of the Automation Policy.
  4. Click Run Automation Policy.
  5. Configure the new task to meet your requirements. For more information, refer to Adding Automation Policy Tasks.
  6. In the Details tab, select the appropriate Automation Policy from the Repository Item drop-down list box.
  7. If the Policy requires configuring an Office 365 Authentication UserName, perform the following:
    1. Select Text input to type a user name or select Asset variable to use a variable for the user name.
    2. If you want to use an Asset variable, select Device Credentials User Name.
  8. If the Policy requires configuring an Office 365 Authentication Password, perform the following:
    1. Select Text input to type a password or select Asset variable to use a variable for the password.
    2. If you want to use an Asset variable, select Device Credentials Password.
  9. Configure the remaining task properties as required.
  10. The Executing Devices tab becomes active when you select the related automation policy. For Office 365, these are the policies with O365 in the name.

  11. Click Save.

SaaS Device Management in MSP N-central

Managing SaaS devices in MSP N-central includes a number of processes.

Delete an SaaS device

  1. In the navigation pane, click Views > All Devices.
  1. Click the SaaS Devices tab.
  2. Select the check box next to the device (or devices) that you want to delete.

    You can select the check box next to the Name column to select all of the devices.

  3. Click Delete.
  4. Click Delete to confirm the deletion.

Add a note to an SaaS device

  1. In the navigation pane, click Views > All Devices.
  2. Click the SaaS Devices tab.
  3. Select the check box next to the device (or devices) that you want to edit.

    You can select the check box next to the Name column to select all of the devices.

  4. Click the Notes tab.
  5. Click Add Note.
  6. Type the text to be added to the device (or devices).
  7. Click Save.

Export information about SaaS devices

  1. In the navigation pane, click Views > All Devices.
  2. Click the SaaS Devices tab.
  3. Select the check box next to the device (or devices) for which you want to export data.

    You can select the check box next to the Name column to select all of the devices.

  4. Click Export.
  5. Select the format of the data export as either CSV or PDF.

    A data file will be exported to the browser.