Sign in to a partner portal with your company Microsoft or Google login

TL;DR — If a partner or supplier supports single sign-on (SSO, one login used across systems), you can usually sign in by choosing "Sign in with Microsoft" or "Sign in with Google" and using your normal work email. If that does not work, the most common fix is that the partner has not added your company domain yet, so send them your exact work email domain and ask them to enable SSO for it. Reading time: ~5 min

Goal

When you are done, you can open the partner or supplier sign-in page, enter your work email, and complete sign-in with your normal company Microsoft 365 or Google Workspace account instead of using a separate password for that partner system.

Prerequisites

• Your work email address, for example you@yourcompany.com
• Access to your normal company sign-in method:
  • Microsoft 365 / Entra ID (identity provider, the system that proves who you are), or
  • Google Workspace
• A browser where you can open a private/incognito window
• The partner or supplier sign-in URL
• If your company uses multi-factor authentication (MFA, a second sign-in check), your phone or authenticator app
• If sign-in fails: a contact at the partner or supplier who can enable SSO for your company domain

Steps

Step 1: Confirm which company login you use

Open one of these URLs in a browser and try your work email:

Microsoft: https://login.microsoftonline.com/
Google: https://accounts.google.com/

What you should see when this succeeds: you can sign in with your work email and reach your normal company account page, mailbox, or app launcher.

Step 2: Open the partner sign-in page in a private window

In your browser, open a private/incognito window, then open the partner or supplier sign-in URL.

Exact menu path examples:

Chrome: Menu (⋮) → New Incognito Window
Edge: Menu (...) → New InPrivate window
Firefox: Menu (☰) → New private window
Safari: File → New Private Window

What you should see when this succeeds: the partner sign-in page opens with no old account already signed in.

Step 3: Start sign-in with your work email

On the partner sign-in page, use one of these exact actions:

Option A: Click "Sign in with Microsoft"
Option B: Click "Sign in with Google"
Option C: Enter your work email address, for example "you@yourcompany.com", then click "Continue" or "Next"

If the page asks how you want to sign in, choose the option that matches your company account provider.

What you should see when this succeeds: you are redirected to your company sign-in page, not asked to create a new partner password.

Step 4: Complete your normal company sign-in

On the Microsoft or Google page, enter your normal company credentials.

Use your usual steps:

1. Enter your work email
2. Enter your company password
3. Approve MFA if prompted
4. If asked "Stay signed in?", choose your normal company preference

What you should see when this succeeds: you return to the partner system and land on its home page, dashboard, or app selection page.

Step 5: If you see an account chooser, pick the correct work account

If the browser shows more than one signed-in account, choose the exact work account you need.

Use this rule:

Pick: you@yourcompany.com
Do not pick: personal Gmail, old employer account, guest account, or shared mailbox

What you should see when this succeeds: the sign-in continues without looping back to the account picker.

Step 6: If sign-in fails, identify the exact failure message

Try again once in the same private window. Then copy the exact error text you see.

Common examples:

"We couldn't find an account for that email"
"Your organization is not configured for single sign-on"
"Need admin approval"
"This user is not assigned to the application"
"Email domain not recognized"

What you should see when this succeeds: you have the exact error message, not a summary from memory.

Step 7: Send the partner the exact information they need

If the partner has not connected your company login yet, send this message and replace the placeholders.

Subject: Please enable SSO for our company login

Hello,

We need to sign in to your system using our company login.

Please enable SSO for our domain:
- Company domain: yourcompany.com
- Test user email: you@yourcompany.com
- Identity provider: Microsoft 365 / Entra ID OR Google Workspace
- Error shown: "paste the exact error here"

If you need our IdP metadata or setup details, please send the exact requirements (SAML or OIDC, ACS URL / redirect URI, entity ID / audience, and any certificate requirements) to our IT team.

What you should see when this succeeds: the partner replies with either "SSO enabled" or a short list of exact setup values they need from your IT team.

Step 8: Retry sign-in after the partner confirms setup

After the partner says SSO is enabled, repeat Steps 2 through 4 in a new private window.

Use the same path:

Private window → partner sign-in URL → enter work email or click Microsoft/Google → complete company sign-in

What you should see when this succeeds: you reach the partner system without creating or resetting a separate password.

Verify it works

Use these checks to prove the full sign-in path works end to end:

1. Open a new private/incognito window
2. Go to the partner sign-in page
3. Enter your work email or click "Sign in with Microsoft" / "Sign in with Google"
4. Complete your company sign-in
5. Close the browser tab
6. Open the partner sign-in page again in the same private window

Expected result:

- First sign-in: you reach the partner home page, dashboard, or landing page
- Second visit: either you are already signed in, or you can sign in again without any "domain not recognized" or "account not found" error
- You are not asked to create a partner-specific password

If the partner system has a profile page, verify the signed-in email matches your work email exactly.

Common pitfalls

You clicked the wrong sign-in option

Mistake: choosing a personal Google account or the wrong Microsoft account from the account chooser.

Symptom: you get "account not found," land in the wrong tenant (company directory), or see no access after sign-in.

Fix: open a new private window and sign in again with the exact work email, for example you@yourcompany.com.

The partner has not enabled your company domain

Mistake: assuming SSO works automatically just because your company uses Microsoft 365 or Google Workspace.

Symptom: errors like "email domain not recognized," "organization not configured," or a prompt to create a separate local password.

Fix: send the Step 7 message with your exact domain and error text to the partner.

Old browser sessions are interfering

Mistake: trying again in a browser already signed in to several accounts.

Symptom: sign-in loops, wrong account gets selected automatically, or you keep returning to the same error.

Fix: use a private/incognito window and start from the partner sign-in URL again.

Your company requires MFA and the prompt was missed

Mistake: closing the browser tab or ignoring the phone approval prompt.

Symptom: sign-in appears to hang, times out, or returns to the login page.

Fix: retry the sign-in and complete the MFA approval on your phone or authenticator app.

You are not assigned access in the partner system

Mistake: SSO is enabled for your domain, but your user account was not granted access inside the partner app.

Symptom: errors like "user is not assigned," "not authorized," or you sign in successfully but see no data.

Fix: ask the partner to assign you@yourcompany.com to the correct organization, role, or supplier account in their system.

Your email domain does not match the domain the partner enabled

Mistake: signing in with an alias or subsidiary domain, such as you@eu.yourcompany.com, when the partner only enabled yourcompany.com.

Symptom: one company email works for some users, but yours gets "domain not recognized."

Fix: ask the partner which exact email domain they enabled and have them add your actual sign-in domain too.

This article was written by an AI system and published pending human review. Verify anything you intend to act on.