Connection Problems

Maintained by: Aether365 Team Audience: Microsoft 365 Global Administrators Scope: Diagnosing and resolving Microsoft tenant connection errors

Tenant Connection Fails During Consent

"Need admin approval" error on Microsoft consent screen

Cause: Your Microsoft tenant requires administrator approval for application consent. You are not signed in as a Global Administrator.

Fix: Sign in to the consent screen as a Global Administrator of the target tenant. If you do not have Global Admin access, share the connection URL with someone who does.

---

"AADSTS700016: Application not found"

Cause: The Aether365 application registration is not visible to your tenant, usually because Microsoft has not completed the multi-tenant registration propagation.

Fix: Wait 5 minutes and try again. If the error persists, contact support@aether365.io.

---

"AADSTS650052: App needs access to a service your organisation does not currently subscribe to"

Cause: Your tenant does not have the required Microsoft license for one of the permissions Aether365 requested.

Fix: Aether365 requires only Microsoft Graph permissions which are available on all Microsoft 365 commercial subscriptions. If you are using a non-commercial or education tenant, some permissions may be unavailable. Contact support@aether365.io with your tenant type.

---

"AADSTS500011: Resource principal was not found"

Cause: A transient Microsoft Entra issue.

Fix: Try the consent flow again after a few minutes.

---

Redirected back to Aether365 but tenant does not appear as connected

Cause: The callback was received but the service principal could not be stored, usually due to a transient database error.

Fix: Try reconnecting the tenant again. If the problem repeats, contact support.

Consent Errors

If the Microsoft consent screen shows an error other than those listed above:

1. Note the exact error code (AADSTS followed by a number)
2. Check the Microsoft AADSTS error codes reference
3. If you cannot resolve it, email support@aether365.io with the AADSTS error code and your Microsoft tenant domain

Tenant Shows as Connected but Scans Fail

If the connection appears active but scans fail with permission errors:

1. Go to Settings > Connections and disconnect the tenant
2. Reconnect the tenant - this re-runs the consent flow and refreshes the service principal
3. A Global Administrator must approve the consent screen again

This is required if:

• The Aether365 service principal was deleted from your tenant
• The consent was revoked
• The Aether365 application permissions changed (requires re-consent)

Cannot Reconnect After Disconnecting

If you disconnect a tenant and then try to reconnect but get an error saying it is "already connected":

1. In Microsoft Entra admin center, navigate to Enterprise Applications
2. Search for "Aether365" and delete the existing service principal
3. Return to Aether365 and run the connection flow again

Multiple Tenants - Wrong Tenant Connected

If you have multiple Microsoft tenants and accidentally connected the wrong one:

1. Disconnect the incorrect tenant from Settings > Connections
2. Click Connect another tenant
3. On the Microsoft sign-in screen, sign in explicitly as a Global Administrator of the correct tenant
4. If Microsoft auto-selects the wrong account, click "Use a different account" on the sign-in screen