MicrosoftOutlook365

The Microsoft 365 connector in Robility is a secure, cloud-based integration that brings Outlook 365, calendars, user profiles, and Microsoft Graph APIs into your automation workflows. It uses OAuth 2.0 authentication for streamlined email sending, calendar management, and more.

Prerequisites

Before using Microsoft 365 with the Robility platform, users must first establish a secure connection between Robility Manager and your organization’s Microsoft Entra ID (formerly Azure AD) environment. This allows you to authenticate securely and leverage Microsoft Graph APIs for your automation workflows.

Depending on your chosen authentication flow, you will need the following credentials from your Microsoft Entra ID App Registration:

1. Client Credentials: You will need the Client ID, Tenant ID, and Client Secret.
2. Authorization Code: You will need the Service Email Address and Password associated with your Microsoft 365 account.

Ensure that your App Registration has the necessary Microsoft Graph API permissions configured to match your workflow requirements.
Note: Before using any Microsoft 365 activity, you must configure the Microsoft 365 App Integration in Robility Manager for the corresponding project.

For detailed information on managing your credentials, refer to the official guide: Microsoft Entra ID App Registrations.

OAuth Callback URL

The Callback URL is critical for the OAuth flow. After user permission, Microsoft 365 sends the authorization code or access token here, allowing Robility to complete authentication. Find it on the “Microsoft 365” Connection page in Robility and add as Redirect URL in your App Registration:
https://robilitydev.sutherlandglobal.com/Robility/AppIntegration/microsoft365Callback
(Copy directly from the Robility connector page.)

Integration Steps

1. Log in to Robility Manager.
2. Go to Projects → App Integrations → Microsoft 365.
3. Click the Settings icon.
4. Choose your authentication type and connect:
    OAuth 2.0 Client Credentials:
      a.Enter Client ID, Tenant ID, Client Secret.
      b.Click Connect.
    OAuth 2.0 Authorization Code:
      a.Click Connect (redirects to Microsoft login).
      b.Enter service email and password.
      c.Verify under Connections

Adding Connections via Activities

1. Drag and drop the desired Microsoft 365 activity into your workflow.
2. Click the Add New Connection hyperlink within the activity properties.
3. You will be redirected to the Robility Manager.
4. Log in and navigate your project.
5. Select Microsoft 365 from the App Integrations menu.
6. Provide the required credentials (OAuth 2.0 Client Credentials or Authorization Code) and click Connect.
7. Return to the workflow, refresh the connection list, and proceed with your automation.

Expiration and Troubleshooting

Robility auto-refreshes OAuth 2.0 tokens if credentials stay valid.

1. Client Credentials: No auto-expiration; fails only if Client Secret or App Registration is revoked/changed.
2. Authorization Code: Refresh token lasts long-term; may revoke on password change, user consent removal, or organization policies.

If an authentication or token expiry error occurs in Robility, reconnect the integration from the Microsoft 365 connector’s Settings page without re-adding it.

Security Best Practices

Robility prioritizes the security of your Microsoft 365 environment by utilizing industry-standard authentication and data protection protocols.

1. Secure Authentication: OAuth 2.0 ensures that your Microsoft credentials are never stored directly by the Robility platform.
2. Principle of Least Privilege: Access is strictly governed by the specific permissions granted in your Azure App Registration; we recommend limiting these to the minimum required for your workflows.
3. Data Encryption: All communication between Robility and Microsoft services is encrypted via secure HTTPS/TLS channels.
4. Credential Maintenance: Client Secrets should be rotated periodically according to your organization’s security policy and updated immediately in the connector settings.