--- title: "Microsoft 365 - Connection" canonical: "https://helpcenter.mindproapps.com/space/sync/1988362266/Microsoft%20365%20-%20Connection" format: markdown --- > ℹ️ **Summary: **Learn establish the Microsoft 365 connection and synchronization with Mindpro Sync. ### **Microsoft 365 authentication** To establish a connection with Microsoft 365, click on the **New Connection** button on the Connections screen. The system will open a pop-up window with a list of options so you can select the Identity Provider you want to connect to. ![Mindpro-1774982056383-2x.png](media://2a7318e9-8ab6-4148-9ec6-14cd8d030e85) From the options available, select **Microsoft 365** as the Identity Provider to connect and fill the fields accordingly: - **Connection Name:** Inform a name for your connection. - **Application (Client) ID: **Inform the Entra ID Application ID. Entra ID allows creating applications and service principal that can be used with role-based access control. When you have applications, hosted services, or automated tools that need to access or modify resources, you can create an identity for the app. Learn more [here](https://docs.microsoft.com/en-us/azure/active-directory/develop/howto-create-service-principal-portal). - **Directory (Tenant) ID:** A tenant represents an organization. It's a dedicated instance of Entra ID that an organization or app developer receives at the beginning of a relationship with Microsoft. That relationship could start with signing up for Entra ID, or Microsoft 365, for example. Click [here](https://docs.microsoft.com/en-us/azure/active-directory/develop/quickstart-create-new-tenant) to learn how to set up a tenant in Entra ID. If you already have a tenant, click [here](https://docs.microsoft.com/en-us/azure/active-directory/fundamentals/active-directory-how-to-find-tenant) to learn how to find it in Entra ID. - **Client Secret: **This is the password of the client secret. If you don't have a client secret yet, click [here](https://docs.microsoft.com/en-us/azure/active-directory/develop/howto-create-service-principal-portal#option-2-create-a-new-application-secret) to see how to create one. > ℹ️ **Keep in mind** > ℹ️ > ℹ️ Microsoft 365 uses Entra ID to manage user identities behind the scenes. It means the authentication process uses the same Entra ID credentials. Click [here](https://docs.microsoft.com/en-us/microsoft-365/enterprise/azure-integration?view=o365-worldwide) to learn more. --- ### **Microsoft 365 Data synchronization** When connected with Microsoft 365, the system will enable the **synchronization tab** where the user can select the attribute fields to sync the user’s data with Jira and to inform the attribute that will contain the user’s manager information. As a pre-configured option, **the system connects to the Email attributes by default**, so no action is required. But if you want to use different IdP user attributes to sync data, select one from the list and click** Save**. ![Mindpro-1774982101263-2x.png](media://56b19ae9-f58f-4464-8ef8-d9fe8c7e0d63) > ℹ️ **Keep in mind** > ℹ️ > ℹ️ The attribute selected for synchronization should contain a **valid email address** as a value informed in the IdP. Once selected, all users will start having their data synchronized by this attribute. --- ### **Microsoft 365 connection** After establishing your authentication and selecting the field for data synchronization with Microsoft 365, a new connection will appear in the list of connections. In this list of connections, you will be able to view the following information and options:   - **Priority **- When you have multiple connections, you can define their priority order using drag and drop. The priority order defines what connection will be the reference for bringing and displaying attributes if a user is found in two or more Identity Providers. - **Status -** Displays the current status of this connection (connected or disconnected). - **Identity Provider** - This shows the Identity Provider used in this connection. - **User match - **Shows the selected attribute field to be used as the key to establish the data synchronization between the Identity Provider and Jira. - **Manager match - **This is the attribute that contains the manager's email/ID. - **Actions -** Connection actions menu with options to edit the details, delete or disconnect the connection. ![Mindpro-1774982151063-2x.png](media://42fc8bf0-172f-4b52-9828-1becfe412785) > ℹ️ **Keep in mind** > ℹ️ > ℹ️ Microsoft 365 uses Entra ID to manage user identities behind the scenes. It means the authentication process uses the same Entra ID credentials. Click [here](https://docs.microsoft.com/en-us/microsoft-365/enterprise/azure-integration?view=o365-worldwide) to learn more. --- ### **Need any help?** Didn’t find what you were looking for? Raise a ticket [here](https://mindpro.atlassian.net/servicedesk/customer/portal/3) or get in touch at [support@mindproapps.com](mailto:support@mindproapps.com)