Sources checked: 12 October 2026.
Before troubleshooting Skype for Business, ask your workplace IT team which service you are expected to use. A consumer Skype account, retired Skype for Business Online and an organization’s on-premises Skype for Business Server are different products.
Check the product’s status first
- Skype for Business Online: Microsoft retired the main service on 31 July 2021. Cloud users moved to TeamsOnly; an old client sign-in workaround cannot bring the service back. See Microsoft’s retirement guidance.
- Skype for Business Server 2015 and 2019: the 2015 and 2019 lifecycle pages show that ordinary extended support ended in October 2025. Having a working installation is different from having a supported deployment.
- Skype for Business Server Subscription Edition: Microsoft lists it as in support when checked on 12 October 2026. Ask IT to confirm your actual server edition and supported client.
- Consumer Skype: it retired on 5 May 2025; its personal-account migration instructions should not be applied to a workplace server.
Checks for an IT-confirmed server deployment
- Use the workplace sign-in identity. Confirm the address with IT. It may differ from your network username; do not substitute a personal Microsoft account or Skype name.
- Refresh saved credentials after a password change. In the Windows client’s sign-in screen, Microsoft documents Delete my sign-in info, followed by signing in again with the current credentials. Use this only for the correct work account, not as a server migration step.
- Check the work-account sign-in separately. If that same account uses Microsoft 365, test it in your organization’s normal web sign-in. A failure there may be an account issue rather than a Skype client issue.
- Report clock or certificate errors to IT. Check whether your device’s date and time are accurate, but follow workplace device policies.
Microsoft’s sign-in guidance documents these account/client checks. Some parts refer to retired systems; use it alongside the lifecycle information above, not as proof that every edition remains supported.
What to give your IT team
Provide the exact error text, client version, device platform, approximate time, whether colleagues are affected and whether work-account web sign-in works. On a Mac, have IT confirm the required sign-in address and client/deployment compatibility. Let administrators check server reachability, certificates, account provisioning and migration status. Do not disable MFA, accept an invalid certificate or weaken workplace network protections to force a connection.
Independent information: Number Customer Care is not affiliated with Microsoft. We cannot access your account, reset your password or provide Microsoft customer support.