Every extra password in a company is another place where something can go wrong: a weak password, a password on a sticky note, a former employee’s account nobody switched off. Signing in with Microsoft solves this in your customer service system the same way it does in the rest of your tools.
How Microsoft sign-in works
The Debesis sign-in screen shows a “Sign in with Microsoft” button. The user picks their Microsoft 365 work account, confirms the sign-in according to company rules — for example in the Microsoft Authenticator app — and lands straight in Debesis.
- Sign-in runs through Microsoft Entra ID (formerly Azure AD).
- There is no separate Debesis password to remember or reset.
- Username-and-password sign-in can run in parallel or be switched off.
MFA under your own policies
Multi-factor authentication (MFA) and Conditional Access are enforced by Microsoft — exactly as your IT team set them up. Debesis relies on those rules instead of running its own separate mechanism. If your company requires approval in an app or sign-in only from trusted devices, the same requirements apply when signing in to Debesis.
Control for administrators
Administrators can switch off username-and-password sign-in and require Microsoft sign-in only. Once an account is disabled in Microsoft 365, it can no longer sign in to Debesis — offboarding happens in one place.
When it matters most
- Companies already on Microsoft 365 that want one account for every tool.
- Teams whose IT department requires MFA for every application holding customer data.
- Organisations with staff turnover — disabling an account in one place blocks sign-in everywhere.
- Companies answering customers’ security questionnaires and audits.
Want to see it in practice? Book a demo — we will show the sign-in on your trial account.