Forum Discussion

rkkf's avatar
rkkf
Copper Contributor
Jul 03, 2026
Solved

Purview HR connector

Hi,

 

I am trying to upload a csv file with resigning users to Purview through the HR connector, following the steps from this documentation (https://learn.microsoft.com/en-us/purview/import-hr-data).

Have set up a power automate flow to create a bearer token and upload the csv file using a POST API to "https://webhook.ingestion.office.com/api/signals" as shown in the Github sample solution and script. However, I run into the following error: "No HTTP resource was found that matches the request URI 'https://40.75.149.147/api/signals'.

The IP seems to change each time I make the API call. Is the URI correct or should I be using another specific URI?

Any help would be greatly appreaciated. Thanks in advance!

api
  • Jamony's avatar
    Jamony
    Jul 03, 2026

    Hi rkkf, I would keep using the documented hostname rather than the changing IP address. Your POST target should stay as https://webhook.ingestion.office.com/api/signals, and DNS/load balancing may resolve it to different backend IPs. Next, check token audience, app permissions, required headers, and CSV schema.

1 Reply

  • Jamony's avatar
    Jamony
    MCT
    Jul 03, 2026

    Hi rkkf, I would keep using the documented hostname rather than the changing IP address. Your POST target should stay as https://webhook.ingestion.office.com/api/signals, and DNS/load balancing may resolve it to different backend IPs. Next, check token audience, app permissions, required headers, and CSV schema.