Forum Discussion
All Copilot Studio Workflow Tools Suddenly Returning HTTP 403 Before Execution
bhaskag, the immediate 403 and missing workflow run make the invocation boundary the first place I would investigate. They do not identify which permission or service rejected the request. The reports here that the maker can succeed while Teams users fail, and that a classic agent behaves differently, are useful comparison cases. I would reproduce with a harmless workflow that only returns a fixed value, using the maker and one affected user in the test pane and published Teams channel.
For each attempt, retain UTC time, environment and agent identifiers, published version, channel, caller, connection configuration and any correlation ID shown. Check Entra sign-in and Conditional Access results for the relevant identity where a corresponding event exists, and check Power Platform service health and connection references. A successful sign-in does not establish authorization to invoke the workflow. If the minimal case fails without a run record, send that comparison to Microsoft support so the pre-execution rejection can be traced. I cannot confirm a service regression or a specific corrective permission from this thread.
My PALO Framework documents this separation in the PALO-AI control path: admitted identity, policy decision, execution receipt and independently observed effect are different evidence: https://paloframework.org/PALO_AIGovernance.html . For this incident, that means identifying the rejecting boundary before changing access, and confirming the target state before retrying any business-changing workflow. PALO-AI is a developer preview; this is a diagnostic application of the published model.