Office 365

SysAid Technical Writer



Office 365

The Office 365 integration allows you to sync SysAid with your Office 365 account so you can automatically log in to SysAid whenever you are logged in to Office 365.


For this integration to work, you must be running SysAid 16.1.25 or higher.


Note: You cannot activate this integration if another single-sign on integration has already been enabled for SysAid.

Set up Office 365 integration in SysAid

The first step to enabling your Office 365 integration is configuring certain parameters from SysAid's Office 365 integration page. Speak to your account manager to ensure that Office 365 is added to your available integrations.

Note: Only an admin with SysAid Administrator permissions can set up this integration.


To configure Office 365 parameters in SysAid:

Configure Callback URL and Issuer in SysAid

  1. Navigate to Settings > Integrations > Third-Party Integrations.
  2. Click the on the Office 365 icon.
  1. In the Office 365 Callback URL field, enter "https://<SYSAID URL>/addons/office365/jsp/consume.jsp".
  2. In the Office 365 Issuer field, enter your Account's Sysaid URL.

Generate the Federation Metadata URL

  1. Login to the Azure Active Directory admin center:
  2. From the left-pane, select Azure Active Directory.
  3. From the left-pane, select App Registration.
  4. Click New Registration.

  5. In the Name field, enter a name for the application (for example "SysAid Login").
  6. Click Register.

  7. Click Manifest.
  8. Search for the signinurl parameter.

  9. Change the parameter to the callback URL you set in SysAid. Make sure it's enclosed with quotes.

  10. Click Save.
  11. Select Overview > Endpoints.

  12. In the Federation Metadata Document URL field, click to copy the URL.

  13. Back in SysAid, paste the contents of the copied field into the Federation Metadata Document URL field.

Fill in the App ID URL field and copy the Application ID

  1. Click X to close the Endpoints screen.
  2. From the side panel, select Authentication.
  3. Click Add a platform.
  4. Click Web.

  5. In the Redirect URI column, add your SysAid account URL.
  6. Click Configure.

  7. Click Overview.
  8. Click Add an Application ID URL.
  9. Click Set.

  10. Paste in SysAid Account URL.

  11. Click Save.

Enable the integration

  1. (Optional) If you want SysAid to create new users with their Office 365 IDs, Enter "Y" in the Create New Users field.
  2. (Optional) You can replace the domain of users that log in to SysAid via Office 365 with any name you want in the Domain Mapping field. This allows you to sync users with their existing names in SysAid.

    To map domains, use the "=" character. You can map multiple domains by entering them in a comma separated list. For example, "MyDomain=, MyDomain2=".

    If you want user names to contain the Office 365 domain, leave this field blank.
  3. Click Save Changes.
  4. Click the Activate Integration slider.

This completes the SysAid Office 365 integration!

When you access your SysAid login screen, you are routed to the Office 365 login screen. If you are logged into Office 365, you are automatically logged in to SysAid.


If you need to manually log in to SysAid to fix your Office 365 configuration, use the following URL: "<SYSAID URL>/Login.jsp?manual=true".


For further assistance, please contact SysAid Support.




How does one do domain mapping for users that were from a LDAP Active Directory account that was using the "sAMAccountName" as the username to Office 365 on a new ".com" domain? For example: "jdoe" to ""
SysAid Technical Writer
Hi R Christensen,

I spoke to our support team and it seems that the integration is not currently set up to map a user name from the AD to a different username in Office 365.

Would you like me to open a feature request for this?

All the best,
I followed all of these steps and can almost get through the sign-in process when I'm redirected to this page by Microsoft.

Did I miss a step with the Reply URL?

This keeps malfunctioning almost every month!

SSO breaks constantly...
We have enabled this integration and it works great but hitting a challenge around quality of data passed into SysAid in the new user object. I have enabled SSO and create new users is set to Y - a user is provisioned the app and it creates a new user object fine. However it only passes limited user information - for example the company field is not passed.

Is there any way to allow additional fields to be passed in SAML token so when user first hits it the additional fields are passed? If not - how would this typically be handled? Some kind of CSV import daily to update user records?
I'm clearly missing something in the setup. It's prompting me to enter the account. I've seen 2 different types of setup for Azure SAML. One shows doing an app registration and one looks like it's half app registration and half custom app setup. I've tried the Office 365 issuer as a number or as our our url, depending on which method I was trying to follow. Which is the right way to do this?
Updated instructions based on the updated portal, etc....would be great. Thanks.

This message was edited 1 time. Last update was at Nov. 07, 2019 03:25 PM


How is it possible to have Multi Tennants from different Azure Directories loging in via SSO on our Cloud Sysaid ticketing system so that we can enable their Ticket portal ?

So different companies to login with their O365 credentials but on Syaid on our cloud tenant.

Can this happen ? - we can't implement SSO because it is single tenant ?
Super SysAider
We have this working for Chrome and Edge but FireFox still asks for a username and password. Anyone have a fix for this?