SecurityIdentity

Your Entra provisioning jobs for GoTo, Vonage and Puzzel need new credentials before spring

Microsoft is retiring Authorization Code Grant for Entra ID provisioning to GoTo, Vonage and Puzzel. Move each job to Client Credentials by March 31, 2027, or new joiners and leavers can stop syncing. Single sign-on isn't affected.

Cohash Security Practice November 2026 12 min read 9 chapters 3-question check
part 12 of 12 · Identity security, from the ground up
01 Entraprovisioning 02 AuthorizationCode retiring 03 31 Mar 2027 04 Clientcredentials

the ideaOne sign-in method retires; give the job its own credentials

after reading, you can
  • Check which Entra provisioning jobs still sign in with Authorization Code Grant
  • Move GoTo, Vonage and Puzzel jobs to client credentials without a sync gap
  • Give each new client secret an owner, so nobody finds out it expired when the sync stops

Microsoft is switching off one of the ways Entra ID signs in to GoTo, Vonage and Puzzel to create and remove users. Jobs still set up the old way can stop after March 31, 2027. Check how each of those provisioning jobs signs in, and move any that still use Authorization Code Grant to Client Credentials before spring.

in plain wordsDeadline: 31 March 2027

If Entra creates your GoTo, Vonage or Puzzel accounts, the way it logs in has to change

If your company lets Microsoft Entra ID, its company directory, look after accounts in GoTo, Vonage or Puzzel, this is for you. A new hire gets a login on day one, and a leaver loses it. To do that, Entra has to sign in to the other product. For GoTo and Vonage, the old setup had an admin click Authorize and log in with their own account, and Entra kept that permission. Microsoft is retiring that method, called Authorization Code Grant, for these three apps. The replacement is a client ID and secret made for Entra in each product's admin portal. Single sign-on keeps working either way. What stops is the account syncing.

think of it like this

Picture a courier who gets into your building because a manager once walked them in and vouched for them. The building now wants every courier to carry their own badge, issued to the courier company. Until you get them a badge, the courier still gets in, but after the cut-off date nobody walks them in any more.

who should care
  • Anyone with GoTo, Vonage or Puzzel fed by Entra
  • Identity admins who own Entra enterprise apps
  • Whoever runs your phones or contact centre
  • IT providers who set Entra up for a client
chapter 01

Why it matters to you

3 appsGoTo, Vonage and Puzzel carry Microsoft's retirement notice
31 Mar 2027Microsoft's migrate-by date for all three
4 weeksIn quarantine that long, an Entra provisioning job is switched off
No changeSingle sign-on to the three apps isn't affected

If a job stops, nothing looks broken on the first day. People already in GoTo or Vonage can still sign in. The trouble builds quietly: new starters wait for a phone or meeting licence, and anyone who left keeps an account until someone notices. In a contact centre, that can be a leaver who still has an agent seat.

Microsoft's wording is careful. After the deadline, jobs still on Authorization Code GrantdefinitionThe OAuth flow where a person logs in and clicks to approve, and the app keeps that approval. It's the one Microsoft is retiring for these jobs. "might stop working and could eventually be removed from the service." Don't read "might" as a grace period. Treat the date as the day your job can start failing.

This is a planned retirement, not a fix for a published vulnerability. It still has an identity angle worth taking seriously. Under the old method a job ran on a permission one admin granted with their own login. Under the new one, it runs on credentials made for the integration, which someone has to own, store and rotate.

what changesThe job used to borrow an admin's login. Now it gets its ownSame Entra provisioning job, same attribute mappings. Only the way it proves who it is changes.
  1. 01 Entra syncs users

    Someone joins or leaves, and Entra adds or disables their account in the app. Nobody does it by hand.

  2. 02 Old sign-in

    An admin clicked Authorize and logged in to GoTo or Vonage with their own account. Entra kept that permission.

  3. 03 Microsoft retires it

    That's the method Microsoft is switching off. Still on it come April, and your job might stop working.

  4. 04 New credentials

    Create a client in the vendor's admin portal and paste its ID, secret, token endpoint and tenant URL into Entra.

  5. 05 Test and run

    Test the connection, provision one user on demand, then let the job carry on.

For engineers: with client credentialsdefinitionThe OAuth option for background jobs. The job swaps a client ID and secret for a short-lived access token, with nobody signing in., Entra sends the client ID and secret to the vendor's token endpointdefinitionWhere Entra trades the client ID and secret for an access token. Each vendor gives you its own, and you paste it into Entra. and gets back a short-lived access token. Nobody has to sign in. Microsoft's guidance for SCIM app makers already calls Authorization Code Grant retired and says existing connectors should use client credentials. So far, GoTo, Vonage and Puzzel are the only apps with a date.

chapter 02

What changed for each app

Where each vendor stands

deprecatedAuthorization Code Grant retired

These jobs lose the old method. Leave one on it past the deadline and Microsoft says it can stop working or be removed.

newGoTo: OAuth client in Organization Center

Create an OAuth client for Entra provisioning in the GoTo Organization Center and paste its client ID and secret into Entra. The old steps had an admin sign in instead.

changedVonage: service credentials in the Admin Portal

Under Account, then User Provisioning, pick Microsoft Entra and generate credentials. New Entra setups default to client credentials already.

changedPuzzel: OIDC client with a shared secret

Add an OIDC client in Puzzel's settings with the Client Credentials grant, set both token lifetimes to 3600 and generate a shared secret.

fixedSingle sign-on untouched

Microsoft says SSO isn't affected. People keep signing in. Only creating, changing and removing accounts stops.

enhancedMappings carry over

Vonage says switching the method doesn't touch schema mappings or the job. The next incremental cycle uses the new credentials.

GoTo's change is the newest. Until this month, Microsoft's GoTo tutorial told you to select Authorize and type a GoTo admin's username and password. If your job was built that way, it's running on that admin's grant today, and it's the one most likely to be forgotten.

Vonage is the furthest along. Its own migration guide says existing jobs won't switch over by themselves, and personal Super User or Account Administrator credentials can't be used for the new method. You generate service credentials instead, so the job no longer depends on one person's account.

Puzzel's tutorial already walks you through client credentials, so a recent Puzzel setup may already be on it. Older ones might not be. Open the job and check before you assume.

tableThe vendors don't quote quite the same dates. Work to Microsoft's, since Entra is the side that stops.
SourceDate it givesWhat it says happens
Microsoft (GoTo, Vonage, Puzzel tutorials)Migrate by 31 Mar 2027Jobs still on Authorization Code Grant might stop and could be removed
Microsoft (Vonage tutorial, capabilities)Supported until 1 Apr 2027Only client credentials after that
Microsoft (Vonage tutorial, setup note)Fallback until 1 Apr 2027The Authorization Code option is removed
Vonage migration guideMigrate by 1 Apr 2027Avoid provisioning interruption
Vonage migration guide, Entra stepsCode Grant until 7 Apr 2027A note in its Entra steps says it stays available until then

How the notices appeared

  1. 22 Oct 2026
    Puzzel tutorial

    Microsoft put the notice on Puzzel's tutorial before the other two. Puzzel admins have had the longest run-up.

  2. 28 Oct 2026
    Vonage tutorial

    Vonage's page now starts you on client credentials. The old method stays only as a fallback for jobs that haven't moved.

  3. 5 Nov 2026
    Vonage's own guide

    Vonage refreshes its own Entra guide. It quotes slightly later dates and adds a troubleshooting table you'll want handy.

  4. 10 Nov 2026
    GoTo tutorial

    GoTo gets the same notice. Its steps now have you create an OAuth client instead of signing in as an admin.

  5. 31 Mar 2027
    Microsoft's deadline

    Jobs still on Authorization Code Grant can stop syncing from here on.

chapter 03

Your options, side by side

There's really one destination here, client credentials. The choice is how and when you get there, and whether you treat it as a five-minute settings change or as a chance to clean up who owns the integration.

side by sideBoth reach client credentials. Only one leaves you knowing who owns the secret
Switch it in March
  • Nobody checks which jobs still use the old method
  • A secret gets made in deadline week, and nobody checks it twice
  • The secret sits in a chat thread. Nobody can find it when it's time to rotate
  • Its expiry date isn't written down anywhere
  • Months later the job goes into quarantine. Nobody remembers there was a secret to renew
Plan it this quarter
  • List every provisioning job and how it signs in. Then you know the size of the job
  • Create the vendor client for a team. People leave, and the job should stay
  • Store the secret in a vault. Write down who owns it and when it runs out
  • Test in a separate Entra app first if the job is busy
  • Point quarantine alerts at a shared inbox first, so a failed switch gets noticed
tableThree ways to make the move
RouteWhen it fitsEffortMain risk
Edit the existing job's Connectivity settingsA small job, or Vonage, where the guide says mappings carry overLow: one change windowA typo or wrong secret quarantines a live job
Build a second app, test, then cut overA large or busy job you can't afford to stallMediumTwo jobs writing to the same accounts if you forget to stop one
Leave it until it failsNeverNone now, a lot laterSilent sync failures, and leavers who keep access

Microsoft's tutorials recommend a separate app when you first try an integration. For a job that provisions thousands of contact-centre agents, that's the safer path. Point the test app at a small group, check the results, then switch the main job and turn the test one off.

chapter 04

Check every job in your tenant

Don't stop at the three apps. Microsoft's SCIM guidance calls the old grant retired for new connectors and steers existing ones to client credentials. When we searched Microsoft's provisioningdefinitionEntra adding, changing and removing someone's account in an app for you, based on whether they're assigned to it. Nobody files a ticket. tutorials, only these three had a date. Zoom's, for one, still has you pick Authorization Code Grant, so find your other jobs now.

Track down every job still on the old sign-in

  1. 01
    List the provisioning apps

    In the Entra admin center, go to Entra ID, then Enterprise apps. Open each app with provisioning switched on and note GoTo, Vonage and Puzzel first.

  2. 02
    Read the sign-in method

    On each app's Provisioning page, open the connection settings and look at the authentication method. Authorization Code Grant is the one to move.

  3. 03
    Find who authorized it

    For an old GoTo or Vonage job, ask who clicked Authorize at go-live. If they've moved on, the job is running on a grant nobody owns.

  4. 04
    Check the job's health

    Look at the status and the provisioning logs. A job already in quarantine needs fixing before you change anything else.

  5. 05
    Check the alerts

    Open Properties and check the Notification Email. Make it a shared inbox, so a quarantine email reaches someone who still works here.

  6. 06
    Write it down

    Put it all in one sheet with a migration date per app. That sheet is your plan now, and your audit evidence later.

chapter 05

What to do now, by role

Who does what before 31 March 2027

Business owner or CISOthis week
  • Ask IT whether Entra creates and removes your GoTo, Vonage or Puzzel users.
  • Get a named owner and a migration date for each one in writing.
  • If an IT provider runs Entra for you, ask them to confirm the switch is booked.
Identity teamthis month
  • Check the authentication method on every provisioning job in the tenant.
  • Set a shared inbox as the notification email on each one.
  • Migrate in a change window. Run Test Connection and on-demand provisioning straight after.
Telephony or contact-centre adminthis month
  • Make the client for Entra in your product's admin portal. Hand the values to the identity team through a vault, never email.
  • On Vonage, put a shared address in the administrator contact email, since that's where credential expiry warnings go.
  • Write down when the secret expires and who rotates it.
Security and auditthis quarter
  • Treat each client secret like an admin password. It belongs in a vault, with access logged.
  • Check leavers from the last month were removed in each app, in case a job has been failing quietly.
  • Put the deadline on the risk register until every job has moved.
chapter 06

Make the new setup last

Client credentials fix the problem of a job running on a person's grant. They bring a new one: a long-lived client secret that Microsoft's own SCIM docs describe as having the permissions the API needs. Someone has to own it, keep it somewhere safe and rotate it before it expires. Vonage's troubleshooting list puts an expired or rotated secret among the causes of a quarantined job.

before

Before: a job running on one admin's grant

A setup we'd worry about. One person authorized it years ago, and quarantine emails go nowhere.

Before: a job running on one admin's grant A setup we'd worry about. One person authorized it years ago, and quarantine emails go nowhere. 01 · MICROSOFT ENTRA ID 02 · VENDOR 03 · AROUND IT Authorization Code granted disables Provisioning job GoTo or Vonage app Notification email not set SCIM API user accounts Admin's login authorized once Who owns it? unknown Leavers removed if the job runs © Cohash · cohash.com
01 · MICROSOFT ENTRA ID02 · VENDOR03 · AROUND IT Provisioning job: GoTo or Vonage app Provisioningjob GoTo or Vonage app Notification email: not set Notificationemail not set SCIM API: user accounts SCIM API user accounts Admin's login: authorized once Admin's login authorized once Who owns it?: unknown Who owns it? unknown Leavers: removed if the job runs Leavers removed if the jobruns Authorization Code granted disables © Cohash · cohash.com
after

After: the integration has its own credentials

Same job and mappings. A client made for Entra, a secret in a vault and alerts that reach a team.

After: the integration has its own credentials Same job and mappings. A client made for Entra, a secret in a vault and alerts that reach a team. 01 · MICROSOFT ENTRA ID 02 · VENDOR 03 · AROUND IT client credentials issued for stored renews Provisioning job tested on demand Notification email shared inbox Token endpoint short-lived tokens Client for Entra named owner Client secret in a vault Rotation date on the calendar © Cohash · cohash.com
01 · MICROSOFT ENTRA ID02 · VENDOR03 · AROUND IT Provisioning job: tested on demand Provisioningjob tested on demand Notification email: shared inbox Notificationemail shared inbox Token endpoint: short-lived tokens Token endpoint short-lived tokens Client for Entra: named owner Client forEntra named owner Client secret: in a vault Client secret in a vault Rotation date: on the calendar Rotation date on the calendar client credentials stored © Cohash · cohash.com

Durable fixes, each tied to this change

  1. 01
    Own the client as a team

    Create the vendor client under a team or service account where the product allows it. When one admin leaves, provisioning shouldn't go with them.

  2. 02
    Keep the secret in a vault

    Copy it once, straight into a secrets manager. Vonage and GoTo both tell you to store it securely, and Vonage only shows it once.

  3. 03
    Rotate in the right order

    Vonage's guide is blunt here: when you rotate the secret in its portal, update Entra immediately, or the job keeps using the old one and fails.

  4. 04
    Send alerts to a team

    Entra sends one email when a job goes into quarantine, plus another if the reason changes. Make sure it lands in a shared inbox.

  5. 05
    Turn on deletion protection

    The Vonage and Puzzel tutorials tell you to switch on accidental deletions prevention. Do it while you're in Properties for the migration.

  6. 06
    Watch for the next notice

    Microsoft says the old grant is retired for new connectors. Keep your job list current so the next app's date is a calendar entry, not a surprise.

chapter 07

If it goes wrong

When accounts stop syncing, after the switch or after the deadline

Most failures here are credentials: a typo, a regenerated secret or a job left on the old method. The bigger job is catching up on the joiners and leavers that didn't sync.

  1. 01Confirm the causefirst hour
    • Check the job's status and read the provisioning logs for the failure.
    • Run Test Connection. If Vonage answers 401 Unauthorized, its guide points at a wrong client ID or secret.
  2. 02Fix the credentialsfirst hour
    • Check all four values were pasted in full: tenant URL, client ID, secret and token endpoint.
    • If the secret was regenerated after you copied it, copy the current one. Generate a new one only if you have to, then update Entra straight away.
  3. 03Get out of quarantinefirst day
    • Once the connection works, watch the next cycle. The job should leave quarantine by itself.
    • Restart provisioning clears quarantine too, but it runs a full initial cycle that takes longer. If the job was disabled after four weeks, restart it.
  4. 04Catch up on leaversfirst day
    • Pull a list of everyone disabled or removed in Entra since the job last ran cleanly. Those are your loose ends.
    • Check those people in GoTo, Vonage or Puzzel by hand, and suspend anything that should have gone.
  5. 05Learn from itthis month
    • Write down who owns the client, where the secret lives and when it expires.
    • Add a check to your joiner and leaver process that spots a stalled job within days.
chapter 08

What this looks like in practice

The companies below are made up. Each one is a setup you could find in a tenant that provisions GoTo, Vonage or Puzzel from Entra, so use them as a checklist for your own.

Three setups you might recognise

01 Entra job 02 Ex-admin'sgrant 03 OAuth client 04 Syncing again
scenario 01High risk
GoTo, authorized by an admin who left
the setup
An accounting firm provisions GoTo from Entra. At go-live an IT admin clicked Authorize and signed in with their own GoTo account. That admin left last year and the job kept running.
what happens
Nobody remembers how the job signs in. After 31 March 2027 it can stop, and new staff wait for GoTo accounts while leavers keep theirs.
what to do
Create an OAuth client in GoTo Organization Center owned by the IT team, switch the job to client credentials, test it and record the owner.
01 Vonage portal 02 New secret 03 Old tokenfails 04 Entra updated
scenario 02Medium risk
A Vonage contact centre, switched in a hurry
the setup
A retailer runs agents on Vonage and provisions them from Entra. The telephony admin generates service credentials on a Friday afternoon, meaning to paste them into Entra on Monday.
what happens
Entra keeps trying with tokens that can't be refreshed, and syncs fail over the weekend. New seasonal agents don't get accounts on Saturday.
what to do
Paste the new values into Entra in the same sitting, run Test Connection, then check the failed users retried on the next cycle.
01 Puzzel job 02 Clientcredentials 03 Secret innotes 04 Vault andowner
scenario 03Low risk
A Puzzel tenant that's already moved
the setup
A healthcare services firm wired up Puzzel provisioning this year. The engineer followed Microsoft's current tutorial, so the job already runs on client credentials.
what happens
The deadline doesn't touch it. The real risk is the shared secret, stored in an engineer's notes with no rotation date.
what to do
Check the method on the Provisioning page anyway. Then move the secret into a vault, and put someone's name and a rotation date next to it.
chapter 09

How Cohash helps

We go through the provisioning apps in your Entra tenant, note how each one signs in, and give every integration credential an owner and a place in a vault. Then we plan and test the switch app by app, in your change windows. The Microsoft Entra ID page covers the wider identity work. You can bring in identity engineers for the clean-up, or ask for an assessment if you'd rather someone looked first. Running Zendesk or Salesforce provisioning from Entra too? Those have their own changes, covered in our Zendesk token post and Salesforce provisioning post.

key takeaways

What to take from this

  1. 01

    GoTo, Vonage and Puzzel jobs can't stay on Authorization Code Grant. Get them moved by 31 March 2027.

  2. 02

    Single sign-on keeps working. Account creation, changes and removals are what stop.

  3. 03

    Vonage says existing jobs won't switch by themselves. Check each job's method on its Provisioning page.

  4. 04

    Generate the vendor credentials and paste them into Entra in one sitting, then test on demand.

  5. 05

    The client secret is the new thing to own. Vault it, name an owner and put the rotation on the calendar.

platforms in this noteMicrosoft Entra ID →
fact-checked November 2026 against vendor and official documentation · where to go next
  1. How Cohash delivers Microsoft Entra ID: scope, roles and architecture
  2. Hire vetted Microsoft Entra ID engineers
  3. Identity governance and administration
  4. Book a 30-minute working session with a senior engineer
01Do I need to do anything if Entra ID provisions our GoTo, Vonage or Puzzel users?

Check how each job signs in. If it uses Authorization Code Grant, move it to Client Credentials before March 31, 2027. If it already uses client credentials, make sure the secret has an owner and a rotation date.

02Will our people still be able to sign in to GoTo, Vonage or Puzzel?

Yes. Microsoft says SSO isn't affected and people already provisioned can keep signing in. What stops is creating new users and syncing changes, including removals.

03What happens if we miss Microsoft's deadline?

Microsoft's words are that those jobs "might stop working and could eventually be removed from the service." While a job's down, new users don't get accounts and leavers aren't removed.

04Will our attribute mappings survive the switch?

Vonage says they do. Changing the sign-in method doesn't touch the schema mappings or the job itself. The next incremental cycle just uses the new credentials.

05How do I tell which method a job uses?

Open the enterprise app in the Entra admin center, go to Provisioning and look at the authentication method in the connection settings. Authorization Code Grant is the one to replace.

06Are other Entra gallery apps affected?

Microsoft's SCIM guidance says Authorization Code Grant is retired, new connectors don't support it and existing ones should use client credentials. Only GoTo, Vonage and Puzzel had a published date when we checked, so keep an eye on the tutorials for the rest.

07Who needs to be involved?

Someone with Cloud Application Administrator, Application Administrator or ownership of the enterprise app in Entra, and an admin in the vendor's portal who can create the client. For Vonage that's an Account Super User, Account Administrator or a partner admin role.

CHOSEN ON A SLIDE DECK Vendor logos on theproposal Quote beforediscovery Juniors swapped inlater Dependency with noexit CHOSEN ON EVIDENCE Named, certifiedstaff Fixed-scopediscovery first References you pick Exit written intocontract
Security · 11 minHow to choose an IAM implementation partner

Ask who will build it, then check they've built one like it before.

read next
next step

Tell us what you're running. We'll tell you what we'd do first.

A 30-minute working session with a senior engineer. No slides.

useful to bring
  • The platform and the version you're on
  • Where you need to get to, and by when
  • What's custom: rules, plugins, integrations
  • Any audit finding or deadline driving it