OVERALL CONTROL / 0.6-customer-control
Grades and scoring
Data access
25% of the overall score before applicability adjustment.
Scored answers and evidence
Read interface 7.5/10
Structured API for the declared product scope
Microsoft Teams / Microsoft Graph v1.0 channel messages and replies, delegated channel posting and channel-message subscriptions; tenant-wide Export APIs and migration-mode writes are separate.
Channel messages are paginated with nextLink and up to 50 root messages per page. Replies need separate traversal or expanded reply pages.
Teams channel message retrieval ↗
Optional query parameters and nextLink · Checked 2026-10-16
Bulk delivery 8.8/10
Batched or iterable API requests
Microsoft Teams / Microsoft Graph v1.0 channel messages and replies, delegated channel posting and channel-message subscriptions; tenant-wide Export APIs and migration-mode writes are separate.
Channel messages are paginated with nextLink and up to 50 root messages per page. Replies need separate traversal or expanded reply pages.
Teams channel message retrieval ↗
Optional query parameters and nextLink · Checked 2026-10-16
Query expressiveness 7.5/10
Fixed object or report retrieval
Microsoft Teams / Microsoft Graph v1.0 channel messages and replies, delegated channel posting and channel-message subscriptions; tenant-wide Export APIs and migration-mode writes are separate.
The list endpoint supports top and expand; other OData filters are not supported on this route.
Teams channel message retrieval ↗
Optional query parameters and nextLink · Checked 2026-10-16
Access cost barrier -
-
Microsoft Teams / Microsoft Graph v1.0 channel messages and replies, delegated channel posting and channel-message subscriptions; tenant-wide Export APIs and migration-mode writes are separate.
Teams licensing, endpoint permission and any separately metered export route must be distinguished. Complete minimum-plan entitlement for this selected route remains unresolved.
Microsoft Graph service throttling limits ↗
Teams service limits · Checked 2026-10-16
Third-party accessibility
20% of the overall score before applicability adjustment.
Scored answers and evidence
Third-party eligibility 10.0/10
Customer authorization without discretionary provider approval
Microsoft Teams / Microsoft Graph v1.0 channel messages and replies, delegated channel posting and channel-message subscriptions; tenant-wide Export APIs and migration-mode writes are separate.
A registered app obtains delegated user consent and required tenant administrator consent. ChannelMessage.Read.All and posting permissions have different requirements; tenant policy controls who can grant them.
Microsoft Graph delegated authorization ↗
User/admin consent and permission scopes · Checked 2026-10-16
Downstream permission -
-
Microsoft Teams / Microsoft Graph v1.0 channel messages and replies, delegated channel posting and channel-message subscriptions; tenant-wide Export APIs and migration-mode writes are separate.
Applicable third-party processing, AI-use and redistribution terms require a separate contractual review.
Microsoft Graph delegated authorization ↗
User/admin consent and permission scopes · Checked 2026-10-16
External action
15% of the overall score before applicability adjustment.
Scored answers and evidence
Write interface 2.5/10
Named operations in a limited domain
Microsoft Teams / Microsoft Graph v1.0 channel messages and replies, delegated channel posting and channel-message subscriptions; tenant-wide Export APIs and migration-mode writes are separate.
Delegated ChannelMessage.Send posts a new channel message. Application-permission posting for migration is a separate constrained route and is not credited here.
Teams channel posting operation ↗
Permissions and request body · Checked 2026-10-16
Custom application path 10.0/10
Customer applications using fixed APIs without provider selection
Microsoft Teams / Microsoft Graph v1.0 channel messages and replies, delegated channel posting and channel-message subscriptions; tenant-wide Export APIs and migration-mode writes are separate.
Customers can build or choose applications using the documented API and the disclosed authorization route.
Microsoft Graph delegated authorization ↗
User/admin consent and permission scopes · Checked 2026-10-16
Continuity
15% of the overall score before applicability adjustment.
Scored answers and evidence
Refresh mechanism 7.5/10
Documented updated-since filters or webhooks
Microsoft Teams / Microsoft Graph v1.0 channel messages and replies, delegated channel posting and channel-message subscriptions; tenant-wide Export APIs and migration-mode writes are separate.
Channel message subscriptions support created, updated and deleted notifications. Subscriptions expire and require renewal; dropped webhook notifications are not recoverable as a durable event log.
Teams message change subscriptions ↗
Channel-level subscriptions and permissions · Checked 2026-10-16
Limit visibility 10.0/10
Published numeric quotas and recovery instructions
Microsoft Teams / Microsoft Graph v1.0 channel messages and replies, delegated channel posting and channel-message subscriptions; tenant-wide Export APIs and migration-mode writes are separate.
Graph publishes Teams-specific endpoint, app and tenant limits rather than one global ceiling. Respect 429 and Retry-After; subscription quotas are separate.
Microsoft Graph service throttling limits ↗
Teams service limits · Checked 2026-10-16
CDC and deletion capture 7.5/10
Updates and deletion identities documented for the stated resources
Microsoft Teams / Microsoft Graph v1.0 channel messages and replies, delegated channel posting and channel-message subscriptions; tenant-wide Export APIs and migration-mode writes are separate.
Channel-message change subscriptions document create, update and delete identities; this does not establish every Teams object or compliance event.
Teams message change subscriptions ↗
Channel-level subscriptions and permissions · Checked 2026-10-16
Microsoft Graph message change semantics ↗
Change notifications create, update and delete; deletedDateTime and channel-local ID · Checked 2026-10-16
Replay and gap recovery 5.0/10
Bounded redelivery or overlapping queries; no durable consumer checkpoint
Microsoft Teams / Microsoft Graph v1.0 channel messages and replies, delegated channel posting and channel-message subscriptions; tenant-wide Export APIs and migration-mode writes are separate.
Graph retries webhook delivery for up to four hours; slow/drop states can discard notifications permanently.
Microsoft Graph webhook delivery ↗
HTTP codes, retries and dropped notifications · Checked 2026-10-16
Data exit
20% of the overall score before applicability adjustment.
Scored answers and evidence
Export custody 7.5/10
Customer-held structured files or API records
Microsoft Teams / Microsoft Graph v1.0 channel messages and replies, delegated channel posting and channel-message subscriptions; tenant-wide Export APIs and migration-mode writes are separate.
Channel-message JSON can be copied while authorized. Replies and referenced SharePoint/OneDrive files need separate reads; a channel export does not establish complete chat or compliance-archive recovery.
Teams channel message copy scope ↗
Messages without replies and paginated JSON responses · Checked 2026-10-16
Post-cancellation access Disclosure
-
Disclosure only; does not reduce planned-exit credit.
Microsoft Teams / Microsoft Graph v1.0 channel messages and replies, delegated channel posting and channel-message subscriptions; tenant-wide Export APIs and migration-mode writes are separate.
The reviewed extraction guide does not establish contractual retrieval rights after cancellation.
Teams channel message copy scope ↗
Messages without replies and paginated JSON responses · Checked 2026-10-16
Planned migration fidelity 7.5/10
Portable structured records on documented routes; whole-product completeness unverified
Microsoft Teams / Microsoft Graph v1.0 channel messages and replies, delegated channel posting and channel-message subscriptions; tenant-wide Export APIs and migration-mode writes are separate.
Channel-message JSON can be copied while authorized. Replies and referenced SharePoint/OneDrive files need separate reads; a channel export does not establish complete chat or compliance-archive recovery.
Teams channel message copy scope ↗
Messages without replies and paginated JSON responses · Checked 2026-10-16
Business logic and customization
5% of the overall score before applicability adjustment.
Scored answers and evidence
Logic authoring 2.5/10
External integration code; native business logic portability not established
Microsoft Teams / Microsoft Graph v1.0 channel messages and replies, delegated channel posting and channel-message subscriptions; tenant-wide Export APIs and migration-mode writes are separate.
Customers can implement external logic against the assessed API. Ownership and reusable export of native workflow artifacts remain unresolved (customer integration code does not establish those rights).
Microsoft Graph delegated authorization ↗
User/admin consent and permission scopes · Checked 2026-10-16
Rights to custom logic -
-
Microsoft Teams / Microsoft Graph v1.0 channel messages and replies, delegated channel posting and channel-message subscriptions; tenant-wide Export APIs and migration-mode writes are separate.
Native workflow ownership, reusable export and independent execution rights remain unresolved.
Microsoft Graph delegated authorization ↗
User/admin consent and permission scopes · Checked 2026-10-16
Scores are out of 10. * Incomplete evidence discounts verified capabilities (unknown answers stay unknown). Planned migration drives data exit. Scoring method ↗
CUSTOMER CHOICE
Third-party accessibility
A registered app obtains delegated user consent and required tenant administrator consent. ChannelMessage.Read.All and posting permissions have different requirements; tenant policy controls who can grant them.
Confirm who can connect, who owns the credentials and which uses are permitted. Customer consent and provider approval can be separate requirements; the selected plan and contract still matter.
READ / INTEGRATE
API and export routes
Channel messages are paginated with nextLink and up to 50 root messages per page. Replies need separate traversal or expanded reply pages. The list endpoint supports top and expand; other OData filters are not supported on this route.
| Access route | Authentication | Credential owner | Provider approval | Access requirement | Last checked |
|---|---|---|---|---|---|
| Customer-authorized application | OAuth 2.0 | Integration provider | No | customer authorization | 2026-10-16 |
Availability depends on your product, plan and agreement. See the documentation below for the requirements of each route.
ECONOMIC ACCESS
Cost, authentication and limits
Teams licensing, endpoint permission and any separately metered export route must be distinguished. Complete minimum-plan entitlement for this selected route remains unresolved.
Check API entitlement, credential ownership and rate limits for the route you intend to use. Include review fees, customer-plan upgrades and ongoing access charges in the total.
ACT FROM OUTSIDE
External action
Delegated ChannelMessage.Send posts a new channel message. Application-permission posting for migration is a separate constrained route and is not credited here.
Validate the supported operation, acting identity and permission scope (read access does not imply write permission). Ambiguous retries and revoked credentials also affect whether an external workflow can run safely.
KEEP ACCESS USEFUL
Continuity
Channel message subscriptions support created, updated and deleted notifications. Subscriptions expire and require renewal; dropped webhook notifications are not recoverable as a durable event log. Graph publishes Teams-specific endpoint, app and tenant limits rather than one global ceiling. Respect 429 and Retry-After; subscription quotas are separate.
CDC, deletions and recovery
| Question | Answer / applicable route | Evidence |
|---|---|---|
| Can ongoing extraction identify updates and deleted records on the declared route? | Updates and deletion identities documented for the stated resourcesMicrosoft Teams / Microsoft Graph v1.0 channel messages and replies, delegated channel posting and channel-message subscriptions; tenant-wide Export APIs and migration-mode writes are separate. Channel-message change subscriptions document create, update and delete identities; this does not establish every Teams object or compliance event. | Teams message change subscriptions ↗Channel-level subscriptions and permissionsChecked 2026-10-16 Microsoft Graph message change semantics ↗Change notifications create, update and delete; deletedDateTime and channel-local IDChecked 2026-10-16 |
| How can extraction recover after missed events or an interrupted consumer? | Bounded redelivery or overlapping queries; no durable consumer checkpointMicrosoft Teams / Microsoft Graph v1.0 channel messages and replies, delegated channel posting and channel-message subscriptions; tenant-wide Export APIs and migration-mode writes are separate. Graph retries webhook delivery for up to four hours; slow/drop states can discard notifications permanently. | Microsoft Graph webhook delivery ↗HTTP codes, retries and dropped notificationsChecked 2026-10-16 |
Useful ongoing access includes corrections and deletions, not only the first export. A failed request, changed filter or lost resource permission should not be interpreted as a deleted record.
LEAVE WITH YOUR DATA
Data exit and portability
Channel-message JSON can be copied while authorized. Replies and referenced SharePoint/OneDrive files need separate reads; a channel export does not establish complete chat or compliance-archive recovery.
Test the output against the destination’s required fields and history. Check stable identifiers, relationships, attachments and extraction time; a sample file proves only the coverage of that sample.
BUILD / INSPECT / REUSE
Business logic and customization
Customers can implement external logic against the assessed API. Ownership and reusable export of native workflow artifacts remain unresolved (customer integration code does not establish those rights).
Custom API access, ownership of workflows and the right to export their definitions are separate questions. A custom-app capability alone does not establish that business rules can move to another system.
AGREEMENTS / API DOCS / PROGRAM REQUIREMENTS
Documented conditions
Answers below come from public provider materials. Every answer retains its source check date, scope (a partner agreement does not describe every customer route). Customer contracts and live behavior still need verification.
| Question | Answer / applicable route | Evidence |
|---|---|---|
| What structured read interface is documented? | Structured API for the declared product scopeMicrosoft Teams / Microsoft Graph v1.0 channel messages and replies, delegated channel posting and channel-message subscriptions; tenant-wide Export APIs and migration-mode writes are separate. Channel messages are paginated with nextLink and up to 50 root messages per page. Replies need separate traversal or expanded reply pages. | Teams channel message retrieval ↗Optional query parameters and nextLinkChecked 2026-10-16 |
| How can customers retrieve data in bulk? | Batched or iterable API requestsMicrosoft Teams / Microsoft Graph v1.0 channel messages and replies, delegated channel posting and channel-message subscriptions; tenant-wide Export APIs and migration-mode writes are separate. Channel messages are paginated with nextLink and up to 50 root messages per page. Replies need separate traversal or expanded reply pages. | Teams channel message retrieval ↗Optional query parameters and nextLinkChecked 2026-10-16 |
| What queries can a customer issue outside the provider UI? | Fixed object or report retrievalMicrosoft Teams / Microsoft Graph v1.0 channel messages and replies, delegated channel posting and channel-message subscriptions; tenant-wide Export APIs and migration-mode writes are separate. The list endpoint supports top and expand; other OData filters are not supported on this route. | Teams channel message retrieval ↗Optional query parameters and nextLinkChecked 2026-10-16 |
| Who decides whether a chosen third party may connect? | Customer authorization without discretionary provider approvalMicrosoft Teams / Microsoft Graph v1.0 channel messages and replies, delegated channel posting and channel-message subscriptions; tenant-wide Export APIs and migration-mode writes are separate. A registered app obtains delegated user consent and required tenant administrator consent. ChannelMessage.Read.All and posting permissions have different requirements; tenant policy controls who can grant them. | Microsoft Graph delegated authorization ↗User/admin consent and permission scopesChecked 2026-10-16 |
| What extra commercial condition applies to the routes supplying the assessed read capability, relative to the lowest paid plan? | -Microsoft Teams / Microsoft Graph v1.0 channel messages and replies, delegated channel posting and channel-message subscriptions; tenant-wide Export APIs and migration-mode writes are separate. Teams licensing, endpoint permission and any separately metered export route must be distinguished. Complete minimum-plan entitlement for this selected route remains unresolved. | Microsoft Graph service throttling limits ↗Teams service limitsChecked 2026-10-16 |
| What permission is needed for the documented downstream use? | -Microsoft Teams / Microsoft Graph v1.0 channel messages and replies, delegated channel posting and channel-message subscriptions; tenant-wide Export APIs and migration-mode writes are separate. Applicable third-party processing, AI-use and redistribution terms require a separate contractual review. | Microsoft Graph delegated authorization ↗User/admin consent and permission scopesChecked 2026-10-16 |
| Which external write operations are documented? | Named operations in a limited domainMicrosoft Teams / Microsoft Graph v1.0 channel messages and replies, delegated channel posting and channel-message subscriptions; tenant-wide Export APIs and migration-mode writes are separate. Delegated ChannelMessage.Send posts a new channel message. Application-permission posting for migration is a separate constrained route and is not credited here. | Teams channel posting operation ↗Permissions and request bodyChecked 2026-10-16 |
| How can customers connect an application they build or choose? | Customer applications using fixed APIs without provider selectionMicrosoft Teams / Microsoft Graph v1.0 channel messages and replies, delegated channel posting and channel-message subscriptions; tenant-wide Export APIs and migration-mode writes are separate. Customers can build or choose applications using the documented API and the disclosed authorization route. | Microsoft Graph delegated authorization ↗User/admin consent and permission scopesChecked 2026-10-16 |
| What mechanism supports repeatable extraction of changes? | Documented updated-since filters or webhooksMicrosoft Teams / Microsoft Graph v1.0 channel messages and replies, delegated channel posting and channel-message subscriptions; tenant-wide Export APIs and migration-mode writes are separate. Channel message subscriptions support created, updated and deleted notifications. Subscriptions expire and require renewal; dropped webhook notifications are not recoverable as a durable event log. | Teams message change subscriptions ↗Channel-level subscriptions and permissionsChecked 2026-10-16 |
| How are integration limits disclosed? | Published numeric quotas and recovery instructionsMicrosoft Teams / Microsoft Graph v1.0 channel messages and replies, delegated channel posting and channel-message subscriptions; tenant-wide Export APIs and migration-mode writes are separate. Graph publishes Teams-specific endpoint, app and tenant limits rather than one global ceiling. Respect 429 and Retry-After; subscription quotas are separate. | Microsoft Graph service throttling limits ↗Teams service limitsChecked 2026-10-16 |
| Where can a usable data copy be delivered? | Customer-held structured files or API recordsMicrosoft Teams / Microsoft Graph v1.0 channel messages and replies, delegated channel posting and channel-message subscriptions; tenant-wide Export APIs and migration-mode writes are separate. Channel-message JSON can be copied while authorized. Replies and referenced SharePoint/OneDrive files need separate reads; a channel export does not establish complete chat or compliance-archive recovery. | Teams channel message copy scope ↗Messages without replies and paginated JSON responsesChecked 2026-10-16 |
| What retrieval rights are documented at cancellation? | -Microsoft Teams / Microsoft Graph v1.0 channel messages and replies, delegated channel posting and channel-message subscriptions; tenant-wide Export APIs and migration-mode writes are separate. The reviewed extraction guide does not establish contractual retrieval rights after cancellation. | Teams channel message copy scope ↗Messages without replies and paginated JSON responsesChecked 2026-10-16 |
| How can customers define their own business logic? | External integration code; native business logic portability not establishedMicrosoft Teams / Microsoft Graph v1.0 channel messages and replies, delegated channel posting and channel-message subscriptions; tenant-wide Export APIs and migration-mode writes are separate. Customers can implement external logic against the assessed API. Ownership and reusable export of native workflow artifacts remain unresolved (customer integration code does not establish those rights). | Microsoft Graph delegated authorization ↗User/admin consent and permission scopesChecked 2026-10-16 |
| What rights or portability are documented for custom workflow artifacts? | -Microsoft Teams / Microsoft Graph v1.0 channel messages and replies, delegated channel posting and channel-message subscriptions; tenant-wide Export APIs and migration-mode writes are separate. Native workflow ownership, reusable export and independent execution rights remain unresolved. | Microsoft Graph delegated authorization ↗User/admin consent and permission scopesChecked 2026-10-16 |
| What usable data or native definitions can leave before cancellation? | Portable structured records on documented routes; whole-product completeness unverifiedMicrosoft Teams / Microsoft Graph v1.0 channel messages and replies, delegated channel posting and channel-message subscriptions; tenant-wide Export APIs and migration-mode writes are separate. Channel-message JSON can be copied while authorized. Replies and referenced SharePoint/OneDrive files need separate reads; a channel export does not establish complete chat or compliance-archive recovery. | Teams channel message copy scope ↗Messages without replies and paginated JSON responsesChecked 2026-10-16 |
SOURCES / SCOPE / HISTORY
Sources and open questions
This review is based on the documentation below. Live account behavior and customer-specific agreements haven’t been tested.
Still to confirm
- Applicable downstream processing and redistribution terms
- Post-cancellation retrieval rights
- Native workflow artifact ownership and independent execution
- Whole-product completeness beyond the declared objects and routes
- Complete commercial entitlement for the assessed portfolio
Documentation
Assessment checked 2026-10-16. Each answer retains its source and applicable route; the check date does not establish live account behavior.