Sign in with Microsoft.
The enterprise hook.

Convert enterprise trials, not procurement battles

For a Microsoft-365 buyer, Continue with Microsoft is the proof that your product fits their stack. Without it, they are filing a vendor security review the day they want to evaluate. With it, they sign in on the homepage with their work account and start using the product the same hour. Synq ships Microsoft OIDC with tenant-targeting and audience controls, so single-tenant customer deployments and multi-tenant SaaS both work cleanly.

Same SDK call as Google

Microsoft is a Synq provider like any other. Your code does not change between providers — only the provider string.

import { SynqProvider, useSynq } from '@synqid/react'
import { SignIn } from '@synqid/react/ui'

export default function App() {
  return (
    <SynqProvider
      issuer="https://api.synq.id"
      clientId={import.meta.env.VITE_SYNQ_CLIENT_ID}
      redirectUri={`${window.location.origin}/auth/callback`}
      theme="dark"
    >
      <Home />
      <SignIn />
    </SynqProvider>
  )
}

function Home() {
  const { signIn } = useSynq()
  return (
    <button onClick={() => signIn({ provider: 'microsoft' })}>
      Continue with Microsoft
    </button>
  )
}

Get it live

Most of the setup happens in Azure Portal. The Synq side is one screen.

1. 1

   Register an app in Azure Portal

   Open Microsoft Entra ID → App registrations → New registration. Pick a supported account type (single-tenant for customer-deployed installs, multi-tenant + personal accounts for SaaS).
2. 2

   Add Synq’s redirect URI

   Under Authentication, add the redirect URI Synq displays in Brand → Connections → Microsoft. Use Web as the platform.
3. 3

   Create a client secret

   Under Certificates & secrets, create a new client secret. Microsoft displays it once — copy it now. Set the expiry to 24 months for ergonomics.
4. 4

   Paste credentials into Synq

   In the Dashboard, open Brand → Connections → Microsoft. Paste the application (client) ID, the tenant ID, and the client secret. Synq encrypts the secret at rest.
5. 5

   Verify the sign-in flow

   Sign in from your app with a Microsoft work or personal account. The consent screen shows your brand. After authorization, Synq issues standard OIDC tokens — no MSAL library on your side.

How Microsoft support compares

Most platforms ship Microsoft. The differences are in how multi-tenant SaaS scenarios and per-brand isolation are handled.

Pair it with

Common questions