Skip to main content

Notifications

Power Automate - General Discussion
Unanswered

outlook.com connector failing with The API version 'V2' has been deprecated.

Posted on 30 Nov 2024 12:48:17 by 6
2 days ago my connection to outlook.com started failing with BadGateway, and in the response json is the message 
The API version 'V2' has been deprecated.
 
{
  "error": {
    "code"502,
    "source""redacted.16.common.australia.azure-apihub.net",
    "clientRequestId""redacted",
    "message""BadGateway",
    "innerError": {
      "status"502,
      "message""The API version 'V2' has been deprecated.\r\nclientRequestId: redacted\r\nserviceRequestId: redacted",
      "error": {
        "message""The API version 'V2' has been deprecated."
      },
      "source""outlook-ae.azconn-ae-001.p.azurewebsites.net"
    }
  }
}
Is anyone else having any luck with outlook.com connections?  These are NOT the office 365 connections.
Categories:
  • CU27080512-0 Profile Picture
    CU27080512-0 6 on 04 Dec 2024 at 11:47:12
    outlook.com connector failing with The API version 'V2' has been deprecated.
    I have my connection working, and I have triple checked that it's on the correct personal account.
    I have successful used a manually triggered flow to list the top 10 emails in a folder, get the content of the emails, parse the content, and choose to delete ones that meet specific criteria.  And since the emails were deleted from the "broken" account, I know it has worked.
     
    I used the graph-explorer to try and retrieve account details and list folders and emails.  I was looking for a difference between my working and broken accounts, and didn't find anything.
    I then went back into make.powerautomate.com and I was able to create a new connection and Switch account to my "broken" personal account.
    I was then able to edit my flows to use the correct connection on all the email steps.
     
    Can someone else try this and see if it magically (I hate to use that term) fixes it for you?
     
    I signed in with my "broken" account, and granted permissions as requested.
    I used at least the following:
    • my profile from Getting Started
    • my high important mail from Outlook Mail
    • my mail that has 'Hello World' from Outlook Mail
    • https://graph.microsoft.com/v1.0/me/mailFolders (it's not listed but I found it though typing stuff in)
    • me from Users
    These are the permissions I ended up granting to Graph Explorer (but those shouldn't have any impact on PowerAutomate as it's a separate app).
    I'm suspecting that one of these tweaked something else to enable the graph api to access my account.
     
     
     
    I did also try to use the testconnection URL's that power automate uses (captured with F12 developer tools) via PostMan using the Access token from graph-explorer, but that didn't work due to 
    "message""Error from token exchange: Bad authorization header scheme"
    which I am hoping isn't what "fixed" things, as that's going to be difficult to provide instructions for.
  • Expiscornovus Profile Picture
    Expiscornovus 30,634 on 04 Dec 2024 at 09:56:35
    outlook.com connector failing with The API version 'V2' has been deprecated.
     
    It seems you are not the only one experiencing this issue. In that case it might be register a support case/ticket with Microsoft as well, reach out to them and see if they can help with this?
     
     
  • PN-04120351-0 Profile Picture
    PN-04120351-0 on 04 Dec 2024 at 04:02:13
    outlook.com connector failing with The API version 'V2' has been deprecated.
    Hi im also Getting this same Error iv tried a few Things and nothing worked so far have any of you got it working again last it was active for me was on the 29th
  • CU03122049-0 Profile Picture
    CU03122049-0 2 on 03 Dec 2024 at 21:03:47
    outlook.com connector failing with The API version 'V2' has been deprecated.
    My "When new mail arrives (V2)" trigger stopped working on 11/5. My connection list showed Outlook.com was connected but any attempt to create an Outlook.com trigger returned the error you're seeing. I deleted Outlook.com from my connections list in an attempt to revalidate my credentials, but it would not reestablish the connection. Hoping a solution will be posted here.
  • CU03122038-0 Profile Picture
    CU03122038-0 2 on 03 Dec 2024 at 20:46:20
    outlook.com connector failing with The API version 'V2' has been deprecated.
    Same issue for me since Nov 29.  Trying to access my personal hotmail account using the Get emails (V2) outlook.com connector.
  • CU03121718-0 Profile Picture
    CU03121718-0 2 on 03 Dec 2024 at 17:23:55
    outlook.com connector failing with The API version 'V2' has been deprecated.
    I've been having the same problem since November 28th. Do you know if Microsoft will solve this issue? I tried to create another account just to check what's going on and it gives the same Badgateway error when I accepted all the permissions.
  • CU27080512-0 Profile Picture
    CU27080512-0 6 on 03 Dec 2024 at 11:39:18
    outlook.com connector failing with The API version 'V2' has been deprecated.
    My previous supposed fix did not work.
    I must have clicked on the wrong personal account.  (Sorry)
     
    One of my personal accounts works, the other personal account fails with the BadGateway and "The API version 'V2' has been deprecated.".
    The one that is failing is the same account as is running the flows.
     
    So I tried to add the bad account in on a different login's make.powerautomate.com outlook.com connection.
    The bad account was unable to be added and fails with the same error.
     
    I have confirmed that the account allows MSFT Power Platform to access it.
    MSFT Power Platform has the same permissions on both accounts.
     
    So I removed the permissions that had been granted to MSFT Power Platform via https://account.microsoft.com/privacy/app-access?refd=account.microsoft.com
    When the app disappeared from the list of approved apps, I then tried to add a connection in make.powerautomate.com.
    This pushed me through the consent process, which added MSFT Power Platform back in, but it still failed with BadGateway.
     
    To be clear I can not create a new outlook.com connection for one of my Personal accounts, it fails with BadGateway.
     
    This Personal account was working up until the 28th of November 2024.
    I can login to the Personal account and view email via outlook.com.
    I have an existing working connection to OneDrive with this Personal account.
    It has permissions granted to the MSFT Power Platform to allow access.
  • CU03121116-0 Profile Picture
    CU03121116-0 2 on 03 Dec 2024 at 11:24:38
    outlook.com connector failing with The API version 'V2' has been deprecated.
    I've been having the same problem since November 28, 2024 my connection to outlook.com started failing with BadGateway.
     
     
     
     
    Anyone else seeing this issue running the same scenario?
  • jgabrielson Profile Picture
    jgabrielson 21 on 02 Dec 2024 at 16:43:50
    outlook.com connector failing with The API version 'V2' has been deprecated.
    I'm also getting this same error now as of Nov 29th 2024.  My flows look for a folder in my outlook.com (personal account) using the V2 "when new email arrives" trigger. As far as I can tell, this connector is still valid but I'm getting the following error in flow checker (personal data XX'd out).  I tried recreating the connection as suggested here but doesn't seem to fix the issue - same error.
     
    {
      "error": {
        "code"502,
        "source""XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX",
        "clientRequestId""XXXXXXXXXXXXXXXXXXXXX",
        "message""BadGateway",
        "innerError": {
          "status"502,
          "message""The API version 'V2' has been deprecated. \r\nclientRequestId: XXXXXXXXXXXXXXXXXXXXXXXX\r\nserviceRequestId: XXXXXXXXXXXXXXXXXX",
    ,
          "error": {
            "message""The API version 'V2' has been deprecated."
          },
          "source""outlook-cc.azconn-cc-001.p.azurewebsites.net"
        }
      }
    }
     
     
    Anyone else seeing this issue running the same scenario?
     
  • CU27080512-0 Profile Picture
    CU27080512-0 6 on 01 Dec 2024 at 10:46:53
    outlook.com connector failing with The API version 'V2' has been deprecated.
    I am using the "When a new email arrives (V2)", which is valid according to the documentation.  I am using it against a personal email account, not a work/enterprise email account.
     
     
    This is what I see when I view the run details showing the failed initiations.
    From what I can determine the 1st thing that the processing does it to test the connections that the flow is using.
    And that fails on outlook.com with the BadGateway.  The other connections that I have pass the test of the connections.
     
    I have another manually run flow, and it is failing with the same issue.  When I try and start it, it fails as well.  Using the development tools in Edge, I can see the http 500 error being returned to my browser, and the URL that is being hit is:
    https://REDACTED.16.common.australia.azure-apihub.net/apim/outlook/REDACTED/testconnection
     
    I have not fixed this.
    To attempt to fix this issue I deleted the outlook.com connections and then recreated them.
    I then went through all my flows and reset the connections to the newly created connection.  The tasks are marked with a Connection warning to help find them, but you still have to check inside any loops or conditions you have.
    I also had to reset any folders that were being used on outlook.com tasks, as otherwise these threw an error.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

November 2024 Newsletter…

November 2024 Community Newsletter…

Community Update Oct 28…

Power Platform Community Update…

Tuesday Tip #7 Community Profile Tips…

Welcome to a brand new series, Tuesday Tips…

Leaderboard

#1
WarrenBelz Profile Picture

WarrenBelz 143,372

#2
RandyHayes Profile Picture

RandyHayes 76,308

#3
Pstork1 Profile Picture

Pstork1 63,900

Leaderboard

Featured topics