When you connect Microsoft Ads to Tracify, Microsoft first signs you in through Microsoft Entra ID (formerly Azure AD). Your organization’s IT policies may restrict whether:
Users can approve (“consent to”) third-party apps
Certain Microsoft services/APIs are enabled for your tenant
Conditional Access rules (device, location, MFA, etc.) block the sign-in
Thus even if you’re a Microsoft Ads admin, your organization may still require an Entra ID admin to approve the connection.
What to do when you see a connection error
Please copy the full error and send it to your IT department
Error code
Correlation ID
Timestamp
These allow your IT team to find the exact failure in Entra sign-in logs. Most of these errors require an Entra ID admin (Global Admin / Cloud App Admin) to approve Tracify or adjust tenant policies.
Common causes
Admin approval / consent required:
Your org doesn’t allow end users to approve third-party apps (or only allows certain apps). IT must approve Tracify.
A required Microsoft service/API isn’t enabled in the tenant:
Example: Microsoft Ads requires access to the Microsoft Advertising API Service. If your tenant doesn’t have the required “service principal,” Microsoft blocks the login until an admin enables/consents to it. This is what errors like AADSTS650052 commonly indicate.
Conditional Access blocks sign-in
Your org requires compliant devices, specific locations, approved apps, etc. IT must exempt/adjust policy for Tracify or ensure you meet requirements.
Specific Errors Guides
Error codes link to in depth guides
Error Code | Reason |
Your Entra (Azure AD) does not recognize Microsoft Advertising API as a known service |