Power Automate keeps bringing error cant contact support button not working.

KELLEN COLEMAN 1 Reputation point
2026-08-31T23:08:07.2733333+00:00

I keep getting an error trying to get into power automate, have used before. Are others experiencing the same?

Microsoft 365 and Office | Install, redeem, activate | Other | Other
0 comments

2 answers

Sort by: Oldest
Most helpful Newest Oldest

  1. AI answer

    2026-08-31T23:08:22.1433333+00:00

    If the Contact support button is failing with an ms-contact-support link required message, the documented fix is to install the Get Help app from the Microsoft Store.

    If Power Automate itself is failing to open or sign in, there are a few known causes:

    1. Two Power Automate for desktop versions are installed This can happen when one version was installed by MSI and another from the Microsoft Store. That combination is unsupported and can cause a Communication error.
      • For Power Automate for desktop 2.34.176.23181 or later or Microsoft Store version 10.0.7118.0 or later:
        • Go to Start > Settings > Apps > Installed apps
        • Search for Power Automate
        • Uninstall one of the two versions
    2. A named pipe conflict is blocking startup On earlier versions, another elevated process can block the required endpoint and prevent Power Automate from starting.
      • Close Power Automate and confirm in Task Manager that it is no longer running.
      • Download and extract Sysinternals Suite.
      • Open an elevated Command Prompt.
      • Run: 
             handle net.pipe
      • Check whether a process is using the string EbmV0LnBpcGU6Ly8rLw==.
      • If found, stop that process, then start Power Automate again.
    3. Sign-in cache is corrupted If the app opens but sign-in fails, delete the token cache file msalcache.bin3 from the correct folder:
      • MSI install: %localappdata%\Microsoft\Power Automate Desktop\Cache\MSI
      • Store install: %localappdata%\Microsoft\Power Automate Desktop\Cache\Store
      After deleting the file, close the Power Automate console, exit it from the system tray or restart the Power Automate service, and try signing in again.
    4. Network access may be blocked If errors include Failed to Fetch, Client Request Aborted, or Network Error, the documented cause is firewall or domain/IP blocking. In that case, the required Power Automate domains and IP addresses need to be allow-listed by IT.

    About whether others are experiencing the same issue: the available context includes community reports of temporary Power Automate access problems and guidance to wait for a Microsoft fix in some cases, so a broader service issue is possible.

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

  2. Kai-H 26,385 Reputation points Microsoft External Staff Moderator
    2026-09-01T09:18:53.2966667+00:00

    Hi, KELLEN COLEMAN

    This may be a temporary service or account-specific issue rather than a problem with the flows themselves. Since the exact error is unclear, first check whether Power Automate works through another access method.

    Besides the solutions provided by the Q&A Assist, here are some suggestions you can try: 

    Open Power Automate on the web in an InPrivate or Incognito window. If it opens there, disable browser extensions, especially ad blockers or privacy tools, and clear the browser cookies for Microsoft sites.

    Try another supported browser, device, or network. Also confirm that you signed in with the same work or school account used previously and selected the correct environment from the environment menu.

    If you use Power Automate for desktop, open Help > Troubleshooter and run the Connectivity and Sign-in checks. The troubleshooter works even when you are not signed in and can produce a report showing what failed.

    Ask your Microsoft 365 or Power Platform administrator to check Support > Service health in the Power Platform admin center. This confirms whether your organization is affected by a known incident.

    If no incident appears, have the administrator create a support request and include the error text, screenshot, time of failure, environment, and any correlation or session ID shown.

    Thank you for your patience in reading, I hope this information has been helpful to you. 

    If the answer is helpful, please click "Yes" and kindly upvote it. If you have extra questions about this answer, please click "Comment."    

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.