Skip to content

Conversation

@dylanstetts
Copy link
Contributor

Added important note about Teams subscription limits and their impact on resource quotas, which was previously unclear.


Add other supporting information, such as a description of the PR changes:

This change clarifies the true tenant limitations for Teams resource subscriptions. This is in response to a customer escalation, incident 21000000814057


Important

The following guidance is for Microsoft employees only. Community contributors can ignore this message; our content team will manage the status.

After you've created your PR, expand this section for tips and additional instructions.
  • do not merge is the default PR status and is automatically added to all open PRs that don't have the ready to merge label.
  • Add the ready for content review label to start a review. Only PRs that have met the minimum requirements for content review and have this label are reviewed.
  • If your content reviewer requests changes, review the feedback and address accordingly as soon as possible to keep your pull request moving forward. After you address the feedback, remove the changes requested label, add the review feedback addressed label, and select the Re-request review icon next to the content reviewer's alias. If you can't add labels, add a comment with #feedback-addressed to the pull request.
  • After the content review is complete, your reviewer will add the content review complete label. When the updates in this PR are ready for external customers to use, replace the do not merge label with ready to merge and the PR will be merged within 24 working hours.
  • Pull requests that are inactive for more than 6 weeks will be automatically closed. Before that, you receive reminders at 2 weeks, 4 weeks, and 6 weeks. If you still need the PR, you can reopen or recreate the request.

For more information, see the Content review process summary.

Added important note about Teams subscription limits and their impact on resource quotas, which was previously unclear.
@dylanstetts dylanstetts added customer support issue Doc issue raised from customer support ready for content review PR is ready for a content review - content development and tech review are complete. labels Dec 19, 2025
@learn-build-service-prod
Copy link
Contributor

Learn Build status updates of commit bfd1be7:

✅ Validation status: passed

File Status Preview URL Details
concepts/includes/change-notifications-supported-resources-expanded.md ✅Succeeded

For more details, please refer to the build report.

@Danipocket Danipocket self-assigned this Dec 23, 2025
@Danipocket Danipocket enabled auto-merge December 23, 2025 15:28
@learn-build-service-prod
Copy link
Contributor

Learn Build status updates of commit e52a597:

✅ Validation status: passed

File Status Preview URL Details
concepts/includes/change-notifications-supported-resources-expanded.md ✅Succeeded

For more details, please refer to the build report.

@Danipocket Danipocket merged commit 3edf3d7 into microsoftgraph:main Dec 23, 2025
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

customer support issue Doc issue raised from customer support ready for content review PR is ready for a content review - content development and tech review are complete.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants