After setting up automatic redirects from HTTP to HTTPS you may start seeing browser warnings about "insecure content" or "mixed content" and some content may be blocked and not displayed, this is because some of the external content references in your html are still using an insecure "http://" url.
Redirecting multiple domains to one and http to https is a pretty common requirement, and the are plenty of examples online showing how to do this using the IIS URL Rewrite Module.
Most of the examples I've seen work fine, but use separate rules for redirecting each domain and for redirecting http to https, resulting in something like this:
I'm a web developer in Sydney Australia and the technical lead at Point Blank Development,
I've been building websites and web applications in Sydney since 1998.