Building and customizing solutions using Microsoft 365 Copilot APIs and tools
Can an individual Visual Studio/MSDN Azure subscription be used to bill Copilot Cowork usage-based billing in an organizational tenant?
Copilot Cowork has moved to General Availability, and we need to activate it for our organization. As part of setup, the Cost Management → spending policy configuration requires an Azure subscription to be attached, so that Cowork usage-based billing (Copilot Credits) can draw from it.
Our organization's Microsoft 365 tenant currently has no Azure subscription attached, and we don't have a partner/CSP managing our billing (we're on direct billing). Separately, we do have an individual Visual Studio/MSDN subscription with a recurring monthly Azure credit, currently associated with a different (personal) Microsoft Entra tenant.
Questions:
- Can an individual Visual Studio/MSDN Azure subscription be moved into an organization's Microsoft 365/Entra tenant (via the "Change Directory" process) and then used as the billing subscription for Copilot Cowork's usage-based billing?
- If moved, does the subscription's monthly Azure credit continue to apply normally, or does anything change once it's associated with a different tenant?
- Is this within the intended use of Visual Studio Subscription Azure credit, or is that credit meant strictly for individual dev/test scenarios rather than organizational production billing?
- Is there a supported way to attach Cowork billing to this kind of subscription without moving its directory (e.g., cross-tenant billing, Azure Lighthouse), or is creating a dedicated org-owned Azure subscription the only supported path?