How to Verify Provider Connectivity in Work 365

Audience: Work 365 Admins, Billing Admins, Support Agents

Overview

In Work 365, provider connectors are managed from Administration → Admin Hub → Integrations. For several provider setup guides, the documented validation pattern is the same: save the connector first, then use the connector’s row-level actions menu to run Verify Connectivity. Work 365 explicitly documents this post-save validation pattern for TD SYNNEX Stellr, TD SYNNEX StreamOne ION, Ingram Micro, Pax8, and Avalara.

A successful result usually means the connector is configured well enough for Work 365 to authenticate and communicate with that provider. If verification fails, the next step should be connector-specific. For most non-Partner Center connectors, Work 365’s setup guides point back to the saved connector values, provider-issued credentials, refresh token state, endpoint selection, or provider-side API enablement.

For Microsoft Partner Center, troubleshooting is different. Current Work 365 guidance focuses on completing both Admin Consent and User Consent in the same Entra tenant that hosts Partner Center, and Microsoft states that not all Partner Center API operations support app-only authentication. Microsoft also enforces MFA for all App+User Partner Center API usage beginning April 1, 2026.

Resolution Steps

Step 1: Open the Integrations page

1. In Work 365, use the area selector in the lower-left corner and switch to Administration.

2. Select Admin Hub.

3. Open the Integrations tab.

Step 2: Locate the provider connector

1. Find the provider integration you want to test.

2. Confirm the connector has already been saved.

3. Open the actions menu on the right side of the connector row. Depending on the connector, this may appear as a gear icon or row actions menu.

Step 3: Run Verify Connectivity

1. Select Verify Connectivity.

2. Wait for the verification result.

3. If the check succeeds, continue with the next connector-specific setup step, such as Sync Provider Accounts where applicable. Work 365 documents this pattern for TD SYNNEX Stellr, TD SYNNEX StreamOne ION, Ingram Micro, Pax8, and Avalara.

Expected Result

If verification succeeds, the connector is still working with the values currently saved in Work 365. In the provider setup guides that document this flow, the usual next step is to continue with Sync Provider Accounts or the next provider-specific configuration task.

If Verification Fails

Treat a failed connectivity check as a connector-specific issue first, not as a general Work 365 platform issue. The correct next step depends on which provider is failing, because the saved configuration requirements differ by connector.

Microsoft Partner Center

For Microsoft Partner Center, recheck the current consent model instead of assuming it is only a saved-credentials issue.

Use this path when Partner Center connectivity appears broken:

1. Confirm the connector was updated using the current Work 365 consent flow.

2. Recheck Admin Consent and User Consent in the same Entra tenant that hosts Partner Center.

3. Confirm the integration user is the dedicated Partner Center integration account recommended by Work 365.

4. Confirm the integration user has the roles Work 365 documents for setup, including Billing admin and Admin agent.

5. Confirm MFA is enabled and working for that integration account. Microsoft states that App+User Partner Center API calls require MFA beginning April 1, 2026, and Work 365’s Partner Center guidance is built around that model.

TD SYNNEX StreamOne ION

For StreamOne ION, review the saved Refresh Token, API Key, API Secret, Account ID, Country, and Currency Code first. Work 365 also warns that the refresh token changes over time, so an older token can break connectivity even if the rest of the connector settings are still correct.

Ingram Micro

For Ingram Micro, recheck the saved Username, Password, API URL, Account ID, Subscription Key, Country, and Currency. Work 365 also notes that its integration uses Ingram Cloud Marketplace (CMP), and partners that have moved fully to XVantage may need to contact Ingram to restore or confirm CMP API access.

Pax8

For Pax8, review the saved Endpoint URL, Application ID, Application Secret, Country Code, Currency Code, and environment-specific settings. Work 365 documents Verify Connectivity as the expected post-save validation step for this connector.

Avalara

For Avalara, review the saved Account ID, License Key, Company ID, Environment, and confirm the connector was saved before testing. Work 365 also instructs admins to return and add the Primary Address after the initial save, then use Verify Connectivity from the connector’s gear menu.

Important Note

“Rerun consent” is the right default remediation for Microsoft Partner Center, but it is not the right default remediation for every provider. For TD SYNNEX, StreamOne ION, Ingram Micro, Pax8, and Avalara, Work 365’s documentation points much more directly to the connector’s saved configuration, provider-issued credentials, refresh token state, API access, or selected environment values.

Troubleshooting Checklist

Before escalating, confirm all of the following:

• The connector was saved before you attempted Verify Connectivity.

• The saved credentials, client secret, refresh token, or subscription key are still valid for that provider.

• The provider-side API access or prerequisite enablement is in place.

• The correct endpoint, environment, country, and currency values were selected where required.

• For Partner Center, both Admin Consent and User Consent were completed in the correct tenant, and MFA is functioning for the integration user.