Skip to content

Conversation

Copy link
Contributor

Copilot AI commented Jan 23, 2026

Users report receiving "Sync Issues to Azure DevOps" emails after Core Components upgrades despite not using Azure DevOps, ALM Accelerator, or Innovation Backlog. Investigation reveals no flow with this name exists—these are Power Platform's automatic failure notifications when the "Admin | Sync Template v3 Configure Emails" flow attempts to configure partially installed or unconfigured optional CoE components.

Changes

New troubleshooting document (docs/TROUBLESHOOTING-AZURE-DEVOPS-EMAILS.md)

  • Root cause: Core Components detects installed solutions and configures them; flows fail if dependencies are missing
  • 5 resolution options: disable flow notifications, turn off unused flows, complete setup, remove unused solutions, or clean up orphaned runs
  • Prevention strategies for future upgrades

Updated main troubleshooting guide (TROUBLESHOOTING-UPGRADES.md)

  • Added "Unexpected Azure DevOps Email Notifications" section to ToC
  • Quick fix with link to detailed guide

Issue response template (docs/issue-response-templates.md)

  • Reusable template explaining this is expected behavior
  • Consistent messaging for maintainers

Improved discoverability (README.md, Documentation/README.md)

  • Added references to troubleshooting resources
  • Better organization of post-upgrade documentation

Key Insight

This is expected behavior, not a bug. Power Platform sends automatic notifications when flows fail. Users receiving these emails have optional CoE components (Innovation Backlog, ALM Accelerator, Pipeline Accelerator) that are installed but not fully configured. Resolution: turn off unused flows or remove unused solutions.

Original prompt

This section details on the original issue you should resolve

<issue_title>Sync Issue to Azure DevOps</issue_title>
<issue_description>### Does this question already exist in our backlog?

  • I have checked and confirm this is a new question.

What is your question?

After reimporting the Core Components for another issue, I am now getting these emails on 'Sync Issues to Azure DevOps...'. We do not use Azure DevOps and the ALM Accelerator is not installed. Is this normal and should just be ignored?

What solution are you experiencing the issue with?

Core

What solution version are you using?

January 2026

What app or flow are you having the issue with?

?

What method are you using to get inventory and telemetry?

None</issue_description>

<agent_instructions>Analyze why emails titled ‘Sync Issues to Azure DevOps…’ are being triggered after re‑importing the Jan 2026 CoE Core Components, even though Azure DevOps and ALM Accelerator are not used or installed. Identify whether this behavior is expected, a misconfiguration, or an unintended dependency, and provide the supported way to disable or stop these notifications.</agent_instructions>

Comments on the Issue (you are @copilot in this section)

Custom agent used: CoE Custom Agent
Specialized agent for triaging and fixing issues in the CoE Starter Kit. Always consult the official CoE docs and the team’s SharePoint notes first, then mine prior GitHub issues and the CoE Common Responses playbook.


✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

Copilot AI and others added 2 commits January 23, 2026 06:44
Co-authored-by: AmarSaiRam <220305901+AmarSaiRam@users.noreply.github.com>
Co-authored-by: AmarSaiRam <220305901+AmarSaiRam@users.noreply.github.com>
Copilot AI changed the title [WIP] Fix sync issue emails related to Azure DevOps Add troubleshooting documentation for post-upgrade flow failure notifications Jan 23, 2026
Copilot AI requested a review from AmarSaiRam January 23, 2026 06:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Sync Issue to Azure DevOps

2 participants