Breaking news from around the world
Get the Bing + MSN extension
Now Available in Community - MBAS 2019 Presentation Videos
Catch the most popular sessions on demand and learn how Dynamics 365, Power BI, PowerApps, Microsoft Flow, and Excel are powering major transformations around the globe. | View Gallery
2019 release wave 2 Discover the latest updates to Dynamics 365Release overview guides and videos Release Plan | Early Access Availability
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Talent TechTalks | Upcoming TechTalks
This post is part of the Enabling Secure Connection for Web Services series.
Over the last few posts, I’ve stepped through the changes to the Web Service configuration files. With all of these changes made, there are a small number of steps to now complte, or confirm as complete.
Firstly, as the configuration files have been changed, the Microsoft Dynamics GP Service Host needs to be restarted. This can be done via the Services control panel applet.
Secondly, ensure the firewall port for the secure port is configured to allow access.
Thirdly, I’d recommend verifying the Web Services are working correctly; when you test the services, use the updated paths for https access:
Read original post Enabling Secure Connection for Web Services: Final Service Configuration at azurecurve|Ramblings of a Dynamics GP Consultant
Business Applications communities