IT_Guy_82 That all depends on your internal DNS - obviously .local won't be accessible from outside your network, but if that's how you intend to operate this system, that's not a problem. I also see you have a "Not secure" warning, so this is a self-signed cert I'm guessing? (again, not a problem if it's only in use by systems that trust this cert).
Do you have some other redirects in place? An SSL cert will NOT redirect traffic, only the web server itself can do that. If the site was set up with a certificate, it's probably worth asking whoever did this, assuming he/she is still available.
As mentioned earlier, I'm no IIS expert, and as this isn't a problem with osTicket, you may get better answers asking on an IIS forum somewhere. Either way, try to ensure you've got somebody in your organisation who knows at least the basics of setting things up here, as this will require ongoing maintenance (when the cert expires, when osTicket is updated, when the requirements update (i.e. new PHP versions), when the Azure SSO needs renewed, etc...).