Fix Modern Authentication Failures During Office 365 Migration
If EdbMails cannot authenticate to a source or target Microsoft 365 tenant, first identify whether the failure occurs during Microsoft sign-in, application registration, admin consent, or after entering Manual Registration details. EdbMails connects to Office 365 using Modern Authentication with OAuth 2.0. Use the checks below to verify the connection without falling back to Basic Authentication or weakening tenant security. For the broader migration solution, see Office 365 migration software.
Identify where authentication is failing
| Symptom | Likely area | What to check / next action |
| Microsoft sign-in does not complete | Account, tenant policy, browser/network, or Microsoft service | Confirm the correct organizational account and tenant. Review sign-in or policy results, verify required Microsoft endpoints are reachable, and retry after resolving the block. |
| Auto Registration fails | Application registration or consent | Use the documented EdbMails Automatic Registration path, sign in with the required administrator account for this method, complete the requested consent, and retry. |
| Manual Registration fails immediately | Registration values | Recheck the Application (client) ID, Directory (tenant) ID, account details, and Client Secret value. Confirm that the secret is valid and has not expired. |
| Authorization or permission error | API permissions or admin consent | Compare the app registration with the current EdbMails Manual Registration guide and confirm the required permissions and admin consent. |
| Connection worked previously but now fails | Policy, application, secret, or session change | Check recent Conditional Access, MFA, app-registration, or client-secret changes. Correct the cause and then authenticate again. |
| Many users fail at once | Tenant, network, or Microsoft service condition | Check Microsoft 365 service health, Microsoft Entra sign-in failures, proxy/firewall changes, and required endpoints before changing EdbMails settings. |
Check these items first
- Confirm that you are signing in to the intended Microsoft 365 tenant with the correct organizational account.
- Check whether browser, pop-up, proxy, firewall, or endpoint restrictions are preventing the Microsoft sign-in flow from completing.
- Review recent changes to MFA, Conditional Access, app registration, permissions, consent, or credentials.
- If failures affect many users at the same time, check Microsoft 365 service health and Microsoft Entra sign-in information before changing the migration configuration.
For a broader pre-migration diagnostic path, use the office 365 migration health checks.
Fix Auto Registration failures
EdbMails provides an Automatic Registration workflow for Office 365 connections. Follow the current EdbMails instructions for this method, including its documented administrator requirement, complete Microsoft sign-in and requested consent, and then retry the connection. Do not generalize this administrator requirement to every Modern Authentication method.
Fix Manual Registration failures
For Manual Registration, verify the Microsoft Entra app registration values entered in EdbMails. Check the Application (client) ID, Directory (tenant) ID, account details, Client Secret value and validity, configured permissions, and required admin consent. Use the current EdbMails registration guide rather than relying on an old permission list or an expired secret.
Check MFA and Conditional Access
Modern Authentication supports Microsoft 365 security controls, but tenant policies can still challenge or block a connection. Review Microsoft Entra sign-in information and the applicable Conditional Access or MFA result to determine why access was interrupted. Do not disable MFA, Conditional Access, Security Defaults, or other tenant protections as a general troubleshooting shortcut. Correct the specific policy or configuration issue that is preventing the approved connection.
Basic Authentication and app passwords should not be treated as the normal fix for current Exchange Online migration authentication failures. Keep the EdbMails connection on the supported Modern Authentication / OAuth 2.0 path.
Retry and validate the connection
- Correct the identified sign-in, registration, consent, permission, policy, network, or credential issue.
- Reconnect the affected source or target in EdbMails and complete Microsoft authentication again where required.
- Confirm that EdbMails can access the intended source or target before resuming migration work.
- Review the migration status and available logs or reports before retrying or continuing a previously interrupted migration.
If authentication is only one part of a larger migration issue, continue with the Office 365 migration guide.
