The real question is should you? :)
The ADFS server doesn't listen on the <IP>:443. It uses the SNI extension of TLS and needs the connexion to be established with the FQDN.
In theory you could add an HTTPS listener for <IP>:443 using NETSH. But then you would also add the IP address as a Subject Alternative Name in your certificate extension. And that's frown upon as IP address could change (so not easy to maintain a certificate) and could be spoofed (although name could also be spoofed). You could also add a default listener for HTTPS with NETSH.
So although possible, I would not advise to do so. Why are you looking at this? Is that for monitoring? If so, let us know what you use for that because most of the load balancer health probing mechanisms do support SNI nowaday.