AtomEmailPro

Microsoft has introduced stricter verification requirements for Outlook accounts.

For some Outlook accounts, a recovery email must be linked before OAuth2 authorization can be enabled. During the authorization process, Microsoft may also require you to verify the recovery email by entering the email address and submitting a verification code.

This is part of Microsoft's account security process, not a requirement created by AtomEmailPro.

What Happens During Outlook OAuth2 Authorization?

When Microsoft requires recovery email verification, the authorization process may look like this:

1. Microsoft asks for the recovery email address.
2. A verification code is sent to that recovery email.
3. The user retrieves the code from the recovery mailbox.
4. The code is entered to complete the verification.
5. OAuth2 authorization can then continue.

The exact verification process is controlled by Microsoft and may vary depending on the Outlook account.

Does AtomEmailPro Currently Support This Verification Process?

At the moment, AtomEmailPro does not support entering the recovery email address and automatically completing the subsequent recovery email verification process.

This means that if Microsoft stops the OAuth2 authorization process and asks for recovery email verification, AtomEmailPro cannot currently complete that additional verification step for you.

This is a limitation of the current AtomEmailPro OAuth2 workflow, not a problem with the email sending function itself.

What About Temporary Recovery Email Services?

Some users use temporary or disposable email services as their Outlook recovery email.

These services may provide access to incoming messages through a special webpage or URL instead of a traditional mailbox login.

For example, a temporary email provider may allow you to open a specific URL to view the verification email and retrieve the Microsoft verification code.

AtomEmailPro currently does not support this type of workflow either.

Supporting it would require AtomEmailPro to:

• Accept the recovery email address
• Access the corresponding recovery mailbox
• Handle the temporary email provider's access method
• Retrieve the Microsoft verification email
• Extract the verification code
• Continue the OAuth2 authorization process

This would be an additional integration with a third-party email service.

Is This a Bug in the Free Version?

No.

It is important to distinguish between a bug and a feature that has not been implemented.

A bug means an existing feature does not work as designed.

In this case, AtomEmailPro does not currently provide a recovery email verification workflow for Outlook OAuth2 authorization.

The fact that a user needs this additional workflow does not mean that the existing OAuth2 functionality is defective.

Microsoft controls the account verification requirements, while AtomEmailPro implements the OAuth2 authorization and email sending functions currently supported by the software.

Can This Be Added?

Potentially, yes.

If you need AtomEmailPro to support a specific recovery email verification workflow, including a particular temporary email service, this can be evaluated as a custom development request.

Because different recovery email services may have completely different access methods, supporting one service does not automatically provide support for every temporary email provider.

If you have a specific workflow that you need, please provide the details of the recovery email service. We can evaluate the technical requirements and determine whether custom development is possible.

A Simple Recommendation

If you plan to use Outlook OAuth2 sending with AtomEmailPro, we recommend using an Outlook account with a recovery email that you can access when Microsoft requests verification.

If Microsoft does not require additional verification, the OAuth2 authorization can proceed normally.

If Microsoft does require recovery email verification, the current version of AtomEmailPro does not yet automate that part of the process.

This is a limitation of the current feature set rather than a bug in the email sending system.