Current restriction on Microsoft Teams (creation of teams using Microsoft Graph API)
Microsoft is currently reporting a malfunction that causes some users and automated processestemporarily do not create Microsoft teams through the Microsoft Graph Create Team APIcan.
This restriction also applies to platforms that automate team creation - e.g. B. Provisioning processes, workflows or deployment pipelines.
Affected functionality
- Creating Microsoft Teams through the Graph API (
/teams) - Automated create team processes with application permissions
- Workflows that query the asynchronous status of a team creation
- Platforms that perform team operations in the background (e.g. B. Provisioning engines)
Microsoft describes the behavior as follows:
- Teams canIntermittently not createdBecome
- The API returns incomplete or incorrect status information
- Async operations deliver incorrect response structures or cancel
Cause
Microsoft has confirmed thatA recent service changecaused regression in the processing of Microsoft asynchronous Microsoft teams operations.
This regression leads to aNon-compliance in operational status processingThis allows team creation to fail through the API.
Status & recommendation
Microsoft Status (Incident TM1230729)
Official Microsoft information can be viewed through the Service Health Center (Incident ID:Tm1230723).
- 11. Feb. 2026, 16:07 CET:
Microsoft identifies regression in the Teams API; mitigations are checked. - 11. Feb. 2026, 19:16 CET:
Microsoft has developed a fix.
The worldwide rollout has oneapprox. 50% coverageachieved.
Delivery continues, monitoring is active.
Effects
- Teams are not created
- Async status queries deliver incorrect or empty values
- Provisioning processes run in error states (Operation Failed)
- Automated deployments can get stuck or cancel
- Mistake isMicrosoft side, not system or configuration-related
Next steps
We actively monitor the global rollout and evaluate in real time whether additional workarounds are necessary.
Parallel we check:
- Renew affected Create Team operations after Microsoft rollout is complete
- Alternative status queries for critical deployments
- Transition mitigations if the fix takes longer
Current status
Last update of this Help Center post: 11. February 2026
Based on the latest Microsoft incident status updateTm1230723In which Microsoft has confirmed the fix and started the global rollout (approx. 50% coverage at the time of publication).
We continuously monitor progress and update this post as new information is available.
Related Articles
Current restriction on Microsoft 365 (Microsoft Graph API)
Microsoft currently has a known issue updating certain properties of Microsoft 365 groups through the Graph API. Particularly affected are the fields: hideFromAddressLists hideFromOutlookClients These settings control the visibility of a group in the ...Current restriction on SharePoint Online (formula fields / Teamsware Studio Deployments)
Currently, some deployments of Teamsware Studio solutions have errors in processes that create or update formula fields in SharePoint. These errors occur exclusively during deployment on productive lists run regularly. Affected functionality ...Known limitation: Authentication of Teamsware app in Microsoft Teams (Error 401)
Description: In the use of theTeamsware appWithin Microsoft Teams, certain content (e.g. B. SharePoint pages or Outlook items) are not loaded. Instead appears an401 ErrorOr the app does not display any data. Cause: This is not a bug of the Teamsware ...