Users may have been unable to run run-only workflows from Microsoft Teams

Title: Users may have been unable to run run-only workflows from Microsoft Teams User impact: Users may be unable to run run-only workflows from Microsoft Teams. More info: As a result of our initial fix deployment, users are now able to run run-only workflows through the "workflows" button in Microsoft Teams. However, running run-only workflows by hovering and selecting "More actions" > "Create workflows" is still an impacted scenario. Affected users are unable to run workflows in Teams when those workflows are configured to be executed by designated users without requiring those users to own or edit the workflow. Users receive the following error message: "Missing Trigger URI" As a way to avoid this issue, impacted users can be granted Owner or Co-owner permissions for the affected workflow. Current status: We’re continuing to validate and test the fix to confirm that it fully remediates the impact without introducing any unintended effects. Scope of impact: Users attempting to run run-only workflows from Microsoft Teams may be impacted. This section may be updated as the investigation progresses. Start time: Tuesday, June 30, 2026, at 7:00 AM UTC Root cause: A recent service update introduced a code regression that affects how Microsoft Teams processes shared workflow requests, preventing some users from running run-only workflows from Microsoft Teams. Next update by: Friday, September 4, 2026, at 8:30 PM UTC

Title: Users may have been unable to run run-only workflows from Microsoft Teams User impact: Users may be unable to run run-only workflows from Microsoft Teams. More info: As a result of our initial fix deployment, users are now able to run run-only workflows through the "workflows" button in Microsoft Teams. However, running run-only workflows by hovering and selecting "More actions" > "Create workflows" is still an impacted scenario. Affected users are unable to run workflows in Teams when those workflows are configured to be executed by designated users without requiring those users to own or edit the workflow. Users receive the following error message: "Missing Trigger URI" As a way to avoid this issue, impacted users can be granted Owner or Co-owner permissions for the affected workflow. Current status: Our process to validate and confirm efficacy of the fix is ongoing, as we work to both ensure successful impact remediation and that there are no adverse effects. Scope of impact: Users attempting to run run-only workflows from Microsoft Teams may be impacted. This section may be updated as the investigation progresses. Start time: Tuesday, June 30, 2026, at 7:00 AM UTC Root cause: A recent service update introduced a code regression that affects how Microsoft Teams processes shared workflow requests, preventing some users from running run-only workflows from Microsoft Teams. Next update by: Friday, August 28, 2026, at 8:30 PM UTC

Title: Users may have been unable to run run-only workflows from Microsoft Teams User impact: Users may be unable to run run-only workflows from Microsoft Teams. More info: As a result of our initial fix deployment, users are now able to run run-only workflows through the "workflows" button in Microsoft Teams. However, running run-only workflows by hovering and selecting "More actions" > "Create workflows" is still an impacted scenario. Affected users are unable to run workflows in Teams when those workflows are configured to be executed by designated users without requiring those users to own or edit the workflow. Users receive the following error message: "Missing Trigger URI" As a way to avoid this issue, impacted users can be granted Owner or Co-owner permissions for the affected workflow. Current status: We're completing the final validations to confirm the efficacy of our secondary fix designed to resolve the impact that occurs when hovering and selecting "More actions" > "Create workflows." We aim to provide a timeline to deployment as soon as possible. Scope of impact: Users attempting to run run-only workflows from Microsoft Teams may be impacted. This section may be updated as the investigation progresses. Start time: Tuesday, June 30, 2026, at 7:00 AM UTC Root cause: A recent service update introduced a code regression that affects how Microsoft Teams processes shared workflow requests, preventing some users from running run-only workflows from Microsoft Teams. Next update by: Wednesday, August 26, 2026, at 8:30 PM UTC

Title: Users may have been unable to run run-only workflows from Microsoft Teams User impact: Users may be unable to run run-only workflows from Microsoft Teams. More info: As a result of our initial fix deployment, users are now able to run run-only workflows through the "workflows" button in Microsoft Teams. However, running run-only workflows by hovering and selecting "More actions" > "Create workflows" is still an impacted scenario. Affected users are unable to run workflows in Teams when those workflows are configured to be executed by designated users without requiring those users to own or edit the workflow. Users receive the following error message: "Missing Trigger URI" As a way to avoid this issue, impacted users can be granted Owner or Co-owner permissions for the affected workflow. Current status: We're continuing to validate the efficacy of a secondary fix designed to resolve the impact that occurs when hovering and selecting "More actions" > "Create workflows." Once a timeline for the deployment of the fix is available, we'll share it accordingly. Scope of impact: Users attempting to run run-only workflows from Microsoft Teams may be impacted. This section may be updated as the investigation progresses. Start time: Tuesday, June 30, 2026, at 7:00 AM UTC Root cause: A recent service update introduced a code regression that affects how Microsoft Teams processes shared workflow requests, preventing some users from running run-only workflows from Microsoft Teams. Next update by: Thursday, August 20, 2026, at 8:30 PM UTC

Title: Users may have been unable to run run-only workflows from Microsoft Teams User impact: Users may be unable to run run-only workflows from Microsoft Teams. More info: As a result of our initial fix deployment, users are now able to run run-only workflows through the "workflows" button in Microsoft Teams. However, running run-only workflows by hovering and selecting "More actions" > "Create workflows" is still an impacted scenario. Affected users are unable to run workflows in Teams when those workflows are configured to be executed by designated users without requiring those users to own or edit the workflow. Users receive the following error message: "Missing Trigger URI" As a workaround, impacted users can be granted Owner or Co-owner permissions for the affected workflow. Current status: Our efforts to validate a secondary fix to remediate the issue in full are ongoing, and we’ll provide a resolution timeline once available. Scope of impact: Users attempting to run run-only workflows from Microsoft Teams may be impacted. This section may be updated as the investigation progresses. Start time: Tuesday, June 30, 2026, at 7:00 AM UTC Root cause: A recent service update introduced a code regression that affects how Microsoft Teams processes shared workflow requests, preventing some users from running run-only workflows from Microsoft Teams. Next update by: Monday, August 17, 2026, at 8:30 PM UTC

Title: Users may have been unable to run run-only workflows from Microsoft Teams User impact: Users may be unable to run run-only workflows from Microsoft Teams. More info: As a result of our initial fix deployment, users are now able to run run-only workflows through the "workflows" button in Microsoft Teams. However, running run-only workflows by hovering and selecting "More actions" > "Create workflows" is still an impacted scenario. Affected users are unable to run workflows in Teams when those workflows are configured to be executed by designated users without requiring those users to own or edit the workflow. Users receive the following error message: "Missing Trigger URI" As a workaround, impacted users can be granted Owner or Co-owner permissions for the affected workflow. Current status: We’re continuing to validate a secondary fix to remediate the issue in full, and we’ll provide an update on the resolution timeline once available. Scope of impact: Users attempting to run run-only workflows from Microsoft Teams may be impacted. This section may be updated as the investigation progresses. Start time: Tuesday, June 30, 2026, at 7:00 AM UTC Root cause: A recent service update introduced a code regression that affects how Microsoft Teams processes shared workflow requests, preventing some users from running run-only workflows from Microsoft Teams. Next update by: Friday, August 14, 2026, at 8:30 PM UTC

Title: Users may have been unable to run run-only workflows from Microsoft Teams User impact: Users may be unable to run run-only workflows from Microsoft Teams. More info: As a result of our initial fix deployment, users are now able to run run-only workflows through the "workflows" button in Microsoft Teams. However, running run-only workflows by hovering and selecting "More actions" > "Create workflows" is still an impacted scenario. Affected users are unable to run workflows in Teams when those workflows are configured to be executed by designated users without requiring those users to own or edit the workflow. Users receive the following error message: "Missing Trigger URI" As a workaround, impacted users can be granted Owner or Co-owner permissions for the affected workflow. Current status: We've confirmed that our initial fix has resolved this issue for running workflows through the "workflows" button in Microsoft Teams. However, less common scenarios such hovering and selecting "More actions" > "Create workflows" are still impacted. We're validating a secondary fix to address all scenarios in which workflows are run in order to fully resolve this event and will provide an update on the timeline of this final deployment by our next scheduled communication. Scope of impact: Users attempting to run run-only workflows from Microsoft Teams may be impacted. This section may be updated as the investigation progresses. Start time: Tuesday, June 30, 2026, at 7:00 AM UTC Root cause: A recent service update introduced a code regression that affects how Microsoft Teams processes shared workflow requests, preventing some users from running run-only workflows from Microsoft Teams. Next update by: Thursday, August 13, 2026, at 8:00 PM UTC

Title: Users may have been unable to run run-only workflows from Microsoft Teams User impact: Users may be unable to run run-only workflows from Microsoft Teams. More info: Affected users are unable to run workflows in Teams when those workflows are configured to be executed by designated users without requiring those users to own or edit the workflow. Users receive the following error message: "Missing Trigger URI" As a workaround, impacted users can be granted Owner or Co-owner permissions for the affected workflow. Current status: We’re performing an extended period of monitoring the telemetry to ensure that our fix has reached all affected users. Scope of impact: Users attempting to run run-only workflows from Microsoft Teams may be impacted. This section may be updated as the investigation progresses. Start time: Tuesday, June 30, 2026, at 7:00 AM UTC Root cause: A recent service update introduced a code regression that affects how Microsoft Teams processes shared workflow requests, preventing some users from running run-only workflows from Microsoft Teams. Next update by: Thursday, July 30, 2026, at 7:30 PM UTC

Title: Users may be unable to run run-only workflows from Microsoft Teams User impact: Users may be unable to run run-only workflows from Microsoft Teams. More info: Affected users are unable to run workflows in Teams when those workflows are configured to be executed by designated users without requiring those users to own or edit the workflow. Users receive the following error message: "Missing Trigger URI" As a workaround, impacted users can be granted Owner or Co-owner permissions for the affected workflow. Current status: We've received confirmation from some affected users that the issue has been mitigated. However, our telemetry indicates that some users are still encountering errors. We're continuing to monitor the telemetry over an extended period to determine when the fix has reached all affected users and fully mitigated the impact. We'll also assess whether any additional mitigation actions are required. Scope of impact: Users attempting to run run-only workflows from Microsoft Teams may be impacted. This section may be updated as the investigation progresses. Start time: Tuesday, June 30, 2026, at 7:00 AM UTC Root cause: A recent service update introduced a code regression that affects how Microsoft Teams processes shared workflow requests, preventing some users from running run-only workflows from Microsoft Teams. Next update by: Thursday, July 30, 2026, at 1:30 AM UTC

Title: Users may be unable to run run-only workflows from Microsoft Teams User impact: Users may be unable to run run-only workflows from Microsoft Teams. More info: Affected users are unable to run workflows in Teams when those workflows are configured to be executed by designated users without requiring those users to own or edit the workflow. Users receive the following error message: "Missing Trigger URI" As a workaround, impacted users can be granted Owner or Co-owner permissions for the affected workflow. Current status: We've confirmed that the reversion has completed and are reaching out to affected users to confirm this has remediated impact. Scope of impact: Users attempting to run run-only workflows from Microsoft Teams may be impacted. This section may be updated as the investigation progresses. Start time: Tuesday, June 30, 2026, at 7:00 AM UTC Root cause: A recent service update introduced a code regression that affects how Microsoft Teams processes shared workflow requests, preventing some users from running workflows from Microsoft Teams. Next update by: Wednesday, July 29, 2026, at 8:30 AM UTC

Title: Users may be unable to run run-only workflows from Microsoft Teams User impact: Users may be unable to run run-only workflows from Microsoft Teams. More info: Affected users are unable to run workflows in Teams when those workflows are configured to be executed by designated users without requiring those users to own or edit the workflow. Users receive the following error message: "Missing Trigger URI" As a workaround, impacted users can be granted Owner or Co-owner permissions for the affected workflow. Current status: We've validated that we're able to revert the responsible change for expedient remediation as we continue to develop our long-term code fix. We anticipate that this reversion will be completed, mitigating impact, by our next scheduled update. Scope of impact: Users attempting to run run-only workflows from Microsoft Teams may be impacted. This section may be updated as the investigation progresses. Start time: Tuesday, June 30, 2026, at 7:00 AM UTC Root cause: A recent service update introduced a code regression that affects how Microsoft Teams processes shared workflow requests, preventing some users from running workflows from Microsoft Teams. Next update by: Tuesday, July 28, 2026, at 7:00 PM UTC

Title: Users may be unable to run run-only workflows from Microsoft Teams User impact: Users may be unable to run run-only workflows from Microsoft Teams. More info: Affected users are unable to run workflows in Teams when those workflows are configured to be executed by designated users without requiring those users to own or edit the workflow. Users receive the following error message: "Missing Trigger URI" As a workaround, impacted users can be granted Owner or Co-owner permissions for the affected workflow. Current status: We’ve determined that a recent service update inadvertently introduced a code regression that affected how Teams processes shared workflow requests, preventing some users from running workflows from Teams. We’re developing a fix and validating it before deployment to the affected environment. Scope of impact: Users attempting to run run-only workflows from Microsoft Teams may be impacted. This section may be updated as the investigation progresses. Start time: Tuesday, June 30, 2026, at 7:00 AM UTC Root cause: A recent service update introduced a code regression that affects how Microsoft Teams processes shared workflow requests, preventing some users from running workflows from Microsoft Teams. Next update by: Monday, July 27, 2026, at 7:00 PM UTC

Title: All users are unable to run Microsoft Teams workflows used to create incidents internally User impact: Users are unable to run Microsoft Teams workflows used to create incidents internally. More info: Users receive the following error message when attempting to create incidents: "Missing Trigger URI" Current status: We're reviewing HTTP Archive (HAR) logs and Teams logs to help identify the root cause and next steps required to mitigate impact. Scope of impact: Users attempting to run run-only workflows from Microsoft Teams may be impacted. This section may be updated as the investigation progresses. Next update by: Monday, July 27, 2026, at 7:00 PM UTC