If your organisation signs in to Mirus Works! using single sign-on (SSO) through your own identity provider (such as Microsoft Entra ID / Azure AD), the SAML signing certificate behind that connection has an expiry date. It needs to be renewed — on your side and ours — before it expires, or your team may be unable to sign in.

When to start

Please get in touch as soon as you know your certificate is due to expire, ideally 4–6 weeks beforehand. The technical update itself is quick, but finding a mutually convenient time for both teams — and avoiding your busy periods — takes longer than people expect.

What we need from you

• Let us know your certificate's expiry date and your preferred change windows (times or days to avoid).
• Once your new certificate is ready, tell us so we can schedule a short cutover call — we ask for at least 3 business days' notice.
• Export and share the new certificate with us ahead of the call (the morning of, at the latest), so our team can review it beforehand.
• Back up your current certificate before we start, as a precaution — we'll do the same on our side. If anything doesn't go to plan, we can revert while we investigate.

What to expect on the day

On the scheduled call, you'll update the certificate on your identity provider and confirm it's done; we'll update the matching configuration on our side. We'll then both test sign-in to confirm SSO is working as expected before we close things out.

Good to know

• There may be a brief interruption to SSO sign-in during the cutover, so we recommend avoiding your own time-sensitive processes (such as payroll exports) during the scheduled window.
• If anything is still in progress on your end that the change window might affect, let us know before we start — we're happy to hold off until you're ready.

Need help?

Contact the Mirus Australia Support team at support@mirusaustralia.com or via your Zendesk portal to get your certificate renewal scheduled.