Unanswered

Proxy web request failed for "Get mail tips for a mailbox (V2)" action

(0) Share

Report

Posted on by CU10010325-0

Hey everyone,

Referring to the subject above, I have been using the "Get mail tips for a mailbox (V2)" action for years now and never got this problem. This has only been happening for the past week (since 6th Jan 2025) and it does not show up as a failed flow or error in Power Automate.

My goal is to get someone's automatic replies from their Outlook to determine if they are out of office or not. Using the action above, in the results body, the following appears:

"body": {
        "@odata.context": "https://graph.microsoft.com/v1.0/$metadata#Collection(microsoft.graph.mailTips)",
        "value": [
            {
                "mailboxFull": false,
                "externalMemberCount": 0,
                "totalMemberCount": 1,
                "deliveryRestricted": false,
                "isModerated": false,
                "maxMessageSize": 37748736,
                "emailAddress": {
                    "name": "",
                    "address": "example@email.com"
                },
                "automaticReplies": {},
                "error": {
                    "message": "Proxy web request failed. ",
                    "code": "NoError"
                }
            }
        ]
    }
 
As you can see in the last few lines, an error message is invoked stating a proxy web request failure. I am not sure if this is an infra issue from our side or there is a problem from Power Automate. Kindly assist or provide any clarification. 

Categories:

General topics

Screenshot 2025-0...

I have the same question (1)

All responses (3)

Answers (0)

Suggested answer

David_MA 12,966 Super User 2025 Season 2 on at

Like (6)

Report
I stopped using the action and now use a call to the Graph API as it seems to have less issues. You can do that with the following steps:

Send an HTTP POST request using the one for Office 365 users

Get the values using a Parse JSON action

Add an Apply to each

What you do in the apply to each action will depend on what you need. But the results come back in an array even if you just run the call on one person.

The flow will look like this:

Here are the values for the above actions:

Compose Action, which returns either the out-of-office notification if it is set, or "Not Set" if it is not set.

coalesce(items('For_each')?['automaticReplies']?['message'],'Not Set')

HTTP Request:

URI: https://graph.microsoft.com/v1.0/users/@{triggerBody()?['email']}/getMailTips

Body: {
"EmailAddresses": ["@{triggerBody()?['email']}"],
"MailTipsOptions": "automaticReplies, mailboxFullStatus"
}

Parse JSON:

{

"type": "object",

"properties": {

"@@odata.context": {

"type": "string"

},

"value": {

"type": "array",

"items": {

"type": "object",

"properties": {

"mailboxFull": {

"type": "boolean"

},

"emailAddress": {

"type": "object",

"properties": {

"name": {

"type": "string"

},

"address": {

"type": "string"

}

}

},

"automaticReplies": {

"type": "object",

"properties": {

"message": {

"type": "string"

},

"messageLanguage": {

"type": "object",

"properties": {

"locale": {

"type": "string"

},

"displayName": {

"type": "string"

}

}

},

"scheduledStartTime": {

"type": "object",

"properties": {

"dateTime": {

"type": "string"

},

"timeZone": {

"type": "string"

}

}

},

"scheduledEndTime": {

"type": "object",

"properties": {

"dateTime": {

"type": "string"

},

"timeZone": {

"type": "string"

}

}

}

}

}

},

"required": [

"mailboxFull",

"emailAddress",

"automaticReplies"

]

}

}

}

}

Was this reply helpful? Yes No
DH-10011752-0 on at

Like (0)

Report
Thank you for posting your solution.

I have seen the same issue which can also be evidenced in Graph Explorer.

Previously this POST command returned the automaticReplies value for any user mailbox:

POST https://graph.microsoft.com/v1.0/me/getMailTips

Starting Tuesday 7th January 2025 this request now only returns results for the logged in user. To view the value for 3 other users (as an example) you would now need 3 separate POST requests:

POST https://graph.microsoft.com/v1.0/users/person1@blah.com/getMailTips POST https://graph.microsoft.com/v1.0/users/person2@blah.com/getMailTips POST https://graph.microsoft.com/v1.0/users/person3@blah.com/getMailTips

I have logged a case with Microsoft to hopefully get this fixed but the issue has not yet been understood or acknowledged.

Was this reply helpful? Yes No
pnthrzrule 64 on at

Like (0)

Report

@DH-10011752-0 did you ever get any response from Microsoft on this?

Was this reply helpful? Yes No