We recently set up CRM with ADFS for a customer. The ADFS service runs on the same server as CRM. Since the ADFS service prefers to run on the default web site with default port bindings, it is recommended to run CRM on different port bindings (not 80 and 443), so we chose 5555 for http and 444 for https. So far so good.
Following the installation instructions for ADFS, we now have one link for external access and one for internal access (say for this thread: https://mycompany.mycompany.com:444 and https://internal.mycompany.com:444)
Everything is working fine, but it is really annoying having to add the :444 at the end of the url. So I tried using the URL Rewrite function in IIS to rewrite requests without port number, but either I am not doing it right, or there are some mechanisms behind the scene (i.e. ADFS related) that prevents the rule from triggering. Either way, nothing is happening, it's like the rule does not exist.
We spent a lot of time getting it to work correctly, so I would rather not move the ADFS service to another server just to have the default bindings on the CRM site again.
Anybody has experience with this and hopefully a workaround..?
