Personalized Community is here!
Quickly customize your community to find the content you seek.
Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2023 Release Wave 1Check out the latest updates and new features of Dynamics 365 released from April 2023 through September 2023
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
Hello Dynamics GP Community!
The support team has been tracking some reports of customers running into issues e-mailing after performing an upgrade to the Fall 2022 release of Dynamics GP (18.5.xxxx). If you've just upgraded to Dynamics GP 18.5 and you're seeing that either you can no longer authenticate or send e-mail you may be running in a scenario where your App Registration in Azure AD needs to be upgraded.
What we are finding is that a change in either Dynamics GP or Azure AD is requiring additional rights under API Permissions in your App Registration in the Azure Portal. When setting up the App Registration we've always directed you to add the Mail.Send delegated MSGraph permission. Well, when a global administrator first authenticates from the Company E-mail Settings window in Dynamics GP 18.5, including granting the requested permissions it will now automatically assign an additional MSGraph permission called Mail.ReadWrite under the "Other permissions granted for %domain%" section of that window:
So, what can you do to address this should you run into any issues? Here's what we would recommend:
You can then test emailing from Dynamics GP and you should see better results. Since this new permission is added automatically during initial authentication and it doesn't exist under "Configured Permissions" we're not going to be changing how the App Registration should be initially setup at this time.
As always, let us know if you have any questions or issues around this.
Business Applications communities