teams-cdp

Topics in the source

• Teams CDP
• Outcome
• Authority and safety
• Prerequisites and commands
• Workflow
• Supported boundary
• Provenance and verification limits

Return structured person/group discovery results, or a new message identifier with the Teams UI's Sent receipt for an authorized exact destination. The next consumer is the calling agent or user. A click, an empty composer, an old matching message, or successful script exit without a receipt is not a send. This skill reuses the current signed-in Teams desktop profile over local CDP. It can request the app's native new-message window; it does not create an independent profile, copy authentication, create a raw Teams browser page, call private Teams APIs, or change operating-system policy. It supports the observed English Teams v2 UI; unsupported or ambiguous UI fails explicitly. Choose an automation-owned native window before discovery/sending. An exact --target is mandatory, but naming a target does not authorize taking over the human's window. Sharing the main window requires explicit user permission and sequential use; never run it concurrently with human interaction. Prefer open-window through the app-provided action in the existing profile. A blank or limited popout is a real stop, not permission to fall back to the main window. The observed client has not established a separat

This is an excerpt. Refer to the complete source and its current requirements.