Hi chriskerrison21
First of all, you should avoid changing any settings in IIS. IIS hosts an internal Sisense component rather than a web application, and must remain with the default settings. Any changes to IIS will likely result in application inaccessibility.
Regarding your task, I see three options:
- Redirect users from the old DNS to a new one instead of assigning both to the same server. This is a common practice - you can host a simple redirection web server on another machine that will redirect users to a new one. This option does not require complex configurations, and you can shut down the redirection server once all users have become accustomed to the new DNS.
- Create a multi-domain SSL certificate and use it to configure SSL in Sisense on the application level. With the multi-domain certificate in place, you can simply assign another DNS name to the same server via CNAME. The SSL configuration in Sisense is done via http://localhost:3030 on the Sisense server. Details: https://docs.sisense.com/win/SisenseWin/setting-up-ssl-for-sisense-windows.htm.
- Configure SSL termination on the Azure side and reconfigure the Sisense application to listen on HTTP. Moving Sisense from SSL to HTTP is also done on the http://localhost:3030 page. At first glance, it appears possible to configure two certificates on the Azure side via Application Gateway (https://learn.microsoft.com/en-us/azure/application-gateway/multiple-site-overviewhttps://learn.microsoft.com/en-us/azure/application-gateway/multiple-site-overview), but you may want to double-check with the Azure support team on the best approach to achieve this task.
Please note that on the Sisense application side, there is an Alias parameter configured on the Admin page. This parameter controls the hyperlinks to Sisense assets in Sisense-generated emails. You will have to set the Alias to one of the domains, as it does not allow multiple entries.
