Issue while running a flow 404 - File or directory not found.

(0) Share

Report

Posted on by CU08091421-0

Trying to run a Scheduled cloud flow where we use Office 365 Management API. The flow is used to send email for service health to user mailbox. It gives error in a particular step where we use http request to retrieve service health incidents and advisories using GET method.

URI : https://manage.office.com/api/v1.0/{tenant_identifier}/ServiceComms/{operation}

Tried using tenant ID/ tenant domain in place of tenant_identifier

operation : Messages

Error : 404 - File or directory not found. The resource you are looking for might have been removed, had its name changed, or is temporarily unavailable.

Please suggest the relevant solutions to fix it.

Categories:

General topics

I have the same question (0)

All responses (2)

Answers (0)

Sort by

Expiscornovus 33,853 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

Hi @CU08091421-0,

Have you tried the Graph API instead?

https://learn.microsoft.com/en-us/graph/api/resources/service-communications-api-overview?view=graph-rest-1.0&preserve-view=true

As far as I am aware they moved the service comms API bit to the Graph a while ago and retired this endpoint.
The service health and communications API in Microsoft Graph is now available, and replaces the Service Communications API

https://practical365.com/moving-office365-service-communications-api-graph/

Happy to help out 😁

I share more #PowerAutomate and #SharePointOnline content on my Blog, LinkedIn, Bluesky profile or Youtube Channel

Was this reply helpful? Yes No
Suggested answer

Inogic 1,291 Moderator on at

Like (0)

Report
Copy link

Link copied!
Hi,

The 404 – File or directory not found error usually happens when the request URI or token setup isn’t quite right. A few things to check:
1. Correct Endpoint Format
The URI should look like this:
https://manage.office.com/api/v1.0/{tenant_id}/ServiceComms/Messages

Replace {tenant_id} with your actual Tenant GUID (not the tenant domain).

2. Permissions
Make sure the Azure AD app used in the flow has the appropriate permission, and that admin consent has been granted.
3. Access Token Scope
The bearer token in your HTTP request must be acquired for the resource:
https://manage.office.com
If the token is generated for https://graph.microsoft.com, it won’t work here.
4. Verify Availability
Not all tenants have the Office 365 Management API enabled. You can test your call in Postman with the right token to confirm if the endpoint responds outside of Power Automate.
Hope this helps.

Thanks!

Inogic

Was this reply helpful? Yes No