Certero Microsoft 365 Connector Credentials Considerations v1
Document version control table
Attribute | Setting |
Document title | Certero Microsoft 365 Connector Credentials Considerations |
Document subject | Identify why a Microsoft 365 connector may have stopped working |
Document version | 1a |
Document category | Standard |
Document published date | 04/03/2025 |
Technical level | 200 |
Hosting type | On premise & SaaS provisioned |
Product name | Certero Unified Platform UI |
Product version | All |
Module | Certero for SaaS Microsoft 365 |
Connector | Certero for SaaS Microsoft 365 Microsoft 365 Connector |
Certero Microsoft 365 Connector
When creating a Microsoft 365 Connector within the Certero platform we need the customer to login into the Azure admin portal
Client ID and Secret
A point to consider here is that part of this process is to input into the Certero platform a Client ID and Client Secret so that we create within the App registration as described above. There are now limitations put in place by Microsoft around the expiration of the Client Secrets. You can set the expiration on a Client Secret to a custom period, up to a maximum of 24 months. The Microsoft recommendation is 6 months, so if a M365 connector fails this is the first area to validate with the customer, and this is the link to share: