Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2021 Release Wave 2Discover the latest updates and new features releasing from October 2021 through March 2022.
2021 release wave 2 plan
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
I have three instances of Dynamic CRM on-Premises (8.1, 8.2, and 9.0). They're all using the same Server 2019 ADFS server and everything works great internally. They're published to the internet using a Server 2019 WAP. I can even log onto the WAP and pull up the IFD URLs for the CRM servers without any issues. When I hit them externally, I'm properly redirected to the ADFS authentication page where I successfully authenticate. Then I'm redirected back to the original CRM URL I requested, the browser spins for a while and then stops and leaves me with a completely blank page. The tab name updates to "Microsoft Dynamics CRM" and viewing page source does have some content in it. So I know something is being passed.
It seems like CRM doesn't like Windows Server 2019 Web Application Proxy. I know it's not officially supported, but has anyone gotten it to work or know why something simple like a WAP would be incompatible with CRM?
I'm posting this here instead of in another forum because publishing a generic html page works fine externally, so I know the WAP works.
Thanks a lot.
indeed CRM 8 does not support Windows Server 2019 and ADFS 5.0 with WAP 2019.
CRM 9.1 does support Windows Server 2019, ADFS 5.0 and WAP 2019. (The official software requirement documentation is updated)
The issue you are facing here is that HTTP/2 on WAP causes the loading problems you are facing.
There is a know problem with WAP already discussed: social.technet.microsoft.com/.../web-application-proxy-2019-sharepoint-2016-and-office-online-server-sites-wont-load
Suggested workaround: (Disable HTTP2)
-> Change needs to be done on the WAP Servers !
Set-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\WinHttp\' -Name EnableDefaultHTTP2 -Value 0
Settings\WinHttp\EnableDefaultHttp2 Type: Dword
Business Applications communities