Outlook.com connector is broken

Question

Outlook.com connector is broken

Max Mayorov 20

Hi,

I have built a Logic App that uses the Outlook.com connector to check and send emails. It was working fine until November 21, when it started returning a 500 error with the following message:

{
    "error": {
        "code": 500,
        "source": "logic-apis-westeurope.azure-apim.net",
        "clientRequestId": "8cd5813a-e0b8-4dd6-95d3-be0aa9d3a912",
        "message": "BadGateway",
        "innerError": {
            "status": 500,
            "message": "Unknown Error : {\"error\":{\"code\":\"Gone\",\"message\":\"The API version 'V2' has been deprecated.\"}}\r\nclientRequestId: 8cd5813a-e0b8-4dd6-95d3-be0aa9d3a912\r\nserviceRequestId: ef01757f-0aee-6409-9644-86e206e9ee5a",
            "error": {
                "message": "Unknown Error : {\"error\":{\"code\":\"Gone\",\"message\":\"The API version 'V2' has been deprecated.\"}}"
            },
            "source": "outlook-we.azconn-we-002.p.azurewebsites.net"
        }
    }
}

How can this issue be resolved? Will the Outlook.com connector be updated? When?

Thank you in advance,

Max

Ryan Hill 30,281 Reputation points Microsoft Employee Moderator

2024-12-04T00:29:11.88+00:00

Hey @Max Mayorov are you using Get Emails v2? Can you share a screen shot or your workflow.json.

Max Mayorov 20

Hi Ryan, thanks for the reply.

I was talking about "Send an Email (v2)": here's a screenshot of the run:

User's image

Here's the code for the failing action:

 "actions": {
                    "Send_an_email_(V2)_1": {
                        "type": "ApiConnection",
                        "inputs": {
                            "host": {
                                "connection": {
                                    "name": "@parameters('$connections')['outlook']['connectionId']"
                                }
                            },
                            "method": "post",
                            "body": {
                                "To": "@variables('to')",
                                "Subject": "@variables('subject')",
                                "Body": "<p class=\"editor-paragraph\">Beste,<br><br>Vind aub de document in bijlage.<br>@{variables('fileName')}<br><br>Groeten,<br>Binary Art Mailing Robot</p>",
                                "Attachments": [
                                    {
                                        "ContentBytes": "@{triggerBody()}",
                                        "Name": "@variables('fileName')"
                                    }
                                ],
                                "Importance": "Normal"
                            },
                            "path": "/v2/Mail"
                        }
                    }
                },

and connection is this (I replaced subscriptionn id with {my-subscription-id}):

           "outlook": {
                    "id": "/subscriptions/{my-subscription-id}/providers/Microsoft.Web/locations/westeurope/managedApis/outlook",
                    "connectionId": "/subscriptions/
{my-subscription-id}
/resourceGroups/binary-art/providers/Microsoft.Web/connections/outlook",
                    "connectionName": "outlook"
                }

Ryan Hill 30,281 Reputation points Microsoft Employee Moderator

2024-12-04T15:06:21.86+00:00

@Max Mayorov can you please respond to the private message.

Accepted answer

0 additional answers

Your answer

Ryan Hill 30,281 Reputation points Microsoft Employee Moderator

2024-12-04T00:29:11.88+00:00

Hey @Max Mayorov are you using Get Emails v2? Can you share a screen shot or your workflow.json.
Max Mayorov 20 Reputation points

2024-12-04T08:41:12.95+00:00

Hi Ryan, thanks for the reply.

I was talking about "Send an Email (v2)": here's a screenshot of the run:

Here's the code for the failing action:

"actions": { "Send_an_email_(V2)_1": { "type": "ApiConnection", "inputs": { "host": { "connection": { "name": "@parameters('$connections')['outlook']['connectionId']" } }, "method": "post", "body": { "To": "@variables('to')", "Subject": "@variables('subject')", "Body": "Beste, Vind aub de document in bijlage. @{variables('fileName')} Groeten, Binary Art Mailing Robot", "Attachments": [ { "ContentBytes": "@{triggerBody()}", "Name": "@variables('fileName')" } ], "Importance": "Normal" }, "path": "/v2/Mail" } } },

and connection is this (I replaced subscriptionn id with {my-subscription-id}):

"outlook": { "id": "/subscriptions/{my-subscription-id}/providers/Microsoft.Web/locations/westeurope/managedApis/outlook", "connectionId": "/subscriptions/ {my-subscription-id} /resourceGroups/binary-art/providers/Microsoft.Web/connections/outlook", "connectionName": "outlook" }
Ryan Hill 30,281 Reputation points Microsoft Employee Moderator

2024-12-04T15:06:21.86+00:00

@Max Mayorov can you please respond to the private message.

Answer 1

Hi @Max Mayorov

I wasn't able to reproduce error. Per our offline discussion, you are no longer seeing this issue.

More than likely, it was an issue with the connector resolving the Outlook API that has since been resolved. I've reached out to the product group for any additional insights. Should I come across any, I'll be sure to update this post.

UPDATE 5 December 2024

The tenant id utilized by the Power Platform connectors was inadvertently removed from the V2 allow list, which resulted in the error message. There is migration path towards MS Graph instead of the V2 API which led to accidental removal. This issue has been mitigated and apologies for the inconvenience.

Share via

Outlook.com connector is broken

0 additional answers

Your answer