Title: Error 422 — unauthorized
Last modified: March 2, 2024

---

# Error 422 — unauthorized

 *  Resolved [Vondelphia.com](https://wordpress.org/support/users/vondelphia/)
 * (@vondelphia)
 * [2 years, 3 months ago](https://wordpress.org/support/topic/error-422-unauthorized/)
 * Same error as many other people “Unauthorized” in the comment section on setting
   up Outlook which I followed perfectly and did twice over (including deleting 
   app and recreating new one). I also checked Email Log and I try to resend but
   same error. Even if I set the “from” email address to match the newly created
   [@outlook](https://wordpress.org/support/users/outlook/).com it doesn’t work…
   plenty or storage space too, it’s a brand new account.
 * [https://fluentsmtp.com/docs/setup-outlook-with-fluentsmtp/](https://fluentsmtp.com/docs/setup-outlook-with-fluentsmtp/)
 *     ```wp-block-code
       Server Response
   
       {
         "code": 422,
         "message": "Unauthorized",
         "errors": [
           "Unauthorized"
         ]
       }
       ```
   
 * Maybe the outlook account being brand new is the issue or the fact that I don’t
   have a charge card linked to the account but I would still suspect a better error
   report.
 * Do I need to make sure I enable any extra API permissions maybe? Or perhaps “
   authorize” a specific domain (or IP address) to use this?
 * **Perhaps the docs are incomplete…**
    -  This topic was modified 2 years, 3 months ago by [Vondelphia.com](https://wordpress.org/support/users/vondelphia/).
    -  This topic was modified 2 years, 3 months ago by [Vondelphia.com](https://wordpress.org/support/users/vondelphia/).
    -  This topic was modified 2 years, 3 months ago by [Vondelphia.com](https://wordpress.org/support/users/vondelphia/).

Viewing 7 replies - 1 through 7 (of 7 total)

 *  Plugin Support [Amimul Ihsan](https://wordpress.org/support/users/amimulihsanmahdi/)
 * (@amimulihsanmahdi)
 * [2 years, 3 months ago](https://wordpress.org/support/topic/error-422-unauthorized/#post-17478594)
 * Hello there,
 * The error is coming from Outlook API calls indicating that there is a problem
   with the authentication. Can you please mention from which email you have generated
   the API key? Also, please check if your outlook account have necessary permission
   to send emails using API key.
 * Thank you
 *  [nebulamedia](https://wordpress.org/support/users/nebulamedia/)
 * (@nebulamedia)
 * [2 years, 3 months ago](https://wordpress.org/support/topic/error-422-unauthorized/#post-17490731)
 * what was the resolution for this, I have the same issue.
 *  Thread Starter [Vondelphia.com](https://wordpress.org/support/users/vondelphia/)
 * (@vondelphia)
 * [2 years, 3 months ago](https://wordpress.org/support/topic/error-422-unauthorized/#post-17490850)
 * No resolution. Same problem since April of last year…
 * I think it’s a combination of both a jenked up coded plugin and a trash outlook
   developer platform [@nebulamedia](https://wordpress.org/support/users/nebulamedia/)
   because things don’t add up… you, me and dozens of other people have the same
   problem and it’s just one of those things that after you spend countless time
   on… you just move on and find a better solution.
 * If the developer re-runs thru the tutorial that’s the day they’ll figure out 
   how to fix things.
 *  [nebulamedia](https://wordpress.org/support/users/nebulamedia/)
 * (@nebulamedia)
 * [2 years, 3 months ago](https://wordpress.org/support/topic/error-422-unauthorized/#post-17490990)
 * [@vondelphia](https://wordpress.org/support/users/vondelphia/), I did find a 
   resolution. Not 100% on this, but it is working on my side now. In Azure Dashboard,
   I enabled the Microsoft Graph API to allow the mail app to send email, and also
   readwrite email. Initially this did not work; however, I believe this is due 
   to the fact that I enabled the API after I had generated the access token. I 
   went back in and regenerated the Access token and the authentication now works
   perfectly.
 *  Thread Starter [Vondelphia.com](https://wordpress.org/support/users/vondelphia/)
 * (@vondelphia)
 * [2 years, 3 months ago](https://wordpress.org/support/topic/error-422-unauthorized/#post-17491291)
 * Incredible [@nebulamedia](https://wordpress.org/support/users/nebulamedia/) —
   thank you very much!
 *  [nebulamedia](https://wordpress.org/support/users/nebulamedia/)
 * (@nebulamedia)
 * [2 years, 3 months ago](https://wordpress.org/support/topic/error-422-unauthorized/#post-17491312)
 * So this worked for you also?
 *  Thread Starter [Vondelphia.com](https://wordpress.org/support/users/vondelphia/)
 * (@vondelphia)
 * [2 years, 3 months ago](https://wordpress.org/support/topic/error-422-unauthorized/#post-17491593)
 * I didn’t try your fix [@nebulamedia](https://wordpress.org/support/users/nebulamedia/)
   because I’m not being paid to work… but, judging by the way you responded, it
   looked and sounded like you got it work so that’s good… now I’ll know in the 
   future if I ever decide to circleback and use the plugin but I don’t think I 
   will because I’ve moved onto using a non-free b$ email provider.
 * 😀

Viewing 7 replies - 1 through 7 (of 7 total)

The topic ‘Error 422 — unauthorized’ is closed to new replies.

 * ![](https://ps.w.org/fluent-smtp/assets/icon.svg?rev=2458343)
 * [FluentSMTP - WP SMTP Plugin with Amazon SES, SendGrid, MailGun, Postmark, Google and Any SMTP Provider](https://wordpress.org/plugins/fluent-smtp/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/fluent-smtp/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/fluent-smtp/)
 * [Active Topics](https://wordpress.org/support/plugin/fluent-smtp/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/fluent-smtp/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/fluent-smtp/reviews/)

 * 7 replies
 * 3 participants
 * Last reply from: [Vondelphia.com](https://wordpress.org/support/users/vondelphia/)
 * Last activity: [2 years, 3 months ago](https://wordpress.org/support/topic/error-422-unauthorized/#post-17491593)
 * Status: resolved