Forum Discussion

JPTutorial's avatar
JPTutorial
Copper Contributor
Jun 30, 2026

[Japan region] Copilot Cowork not showing in the agents list despite all settings enabled

Hello, I'm based in Japan and my tenant region is Japan. I'm trying to enable the now-GA Copilot Cowork for my tenant, but Cowork does not appear in the agents list in the Microsoft 365 admin center, so I can't deploy it.

 

Environment:

 

Location / tenant region: Japan

License: Microsoft 365 Copilot (assigned to target users and the admin account)

All prerequisites appear to be in place and verified:

 

Anthropic (AI provider acting as a Microsoft subprocessor): enabled

Usage-based billing (Copilot Credits): enabled

Discovery setting "AI experiences enabled by usage-based billing": set to allow users to discover and use

Issue: Even with all of the above enabled, searching for "Cowork" under Integrated Apps → All agents returns no result. It also does not appear under Copilot → Settings → View all. As a result, I cannot deploy it to users, and Cowork does not show up for users at m365.cloud.microsoft either.

 

Questions:

 

Is there any additional setting required to make Cowork appear in the agents list?

For a tenant in the Japan region, if there is a delay before the Cowork agent is provisioned after GA, what is the typical timeframe, and is there a way to check the rollout status for my tenant?

Is there a specific admin role (e.g., AI Administrator) I should double-check on the account performing these steps?

If anyone in the Japan region has resolved the same issue, I'd appreciate hearing how. Thank you.

management and extensibility
microsoft 365 copilot
Microsoft 365 Copilot Admin
troubleshooting

1 Reply

  • Jamony's avatar
    Jamony
    MCT
    Jul 02, 2026

    Hi, if all prerequisites and licenses look correct, I’d treat this as either a rollout/region availability issue or an admin-center visibility delay. I’d check the Microsoft 365 admin center message center and roadmap notes for Japan tenant availability, then confirm that agent-related settings are enabled for the target users and that the users are not blocked by a policy or group assignment. It is also worth waiting for propagation after policy changes, but if this has been more than a day or two, I’d open a Microsoft support ticket with the tenant region, license assignment, and screenshots of the enabled settings.