[CoE Starter Kit - BUG] Admin | Audit Logs | Sync Audit Logs (V2) not working correctly with 401 error #6023
Labels
coe-starter-kit
CoE Starter Kit issues
duplicate
This issue or pull request already exists
question
Further information is requested
Does this bug already exist in our backlog?
Describe the issue
We are attempting to convert to the "Sync Audit Logs" flow within the Core solution from the deprecated "Audit Logs" solution. When we run the "Admin | Audit Logs | Office 365 Management API Subscription" flow with START we get a 401 error instead of a 400. When we attempt to run the new "Admin | Audit Logs | Sync Audit Logs (V2)" flow, we also get a 401 error.
Following the documentation here
Since we are coming from previous solution, App registrations is already complete:
API permissions:
Certificates & secrets
Environment Variables:
"Admin | Audit Logs | Office 365 Management API Subscription" results after being run with START:
OUTPUTS Body:
{
"error": {
"code": "AF10001",
"message": "The permission set () sent in the request does not include the expected permission."
}
}
OUTPUTS Body:
{
"operation": "START",
"response": "{"error":{"code":"AF10001","message":"The permission set () sent in the request does not include the expected permission."}}",
"statuscode": "401"
}
The flow completed with Success despite the error.
Assuming this was normal, tested the new "Admin | Audit Logs | Sync Audit Logs (V2)" and received a Failed status:
Expected Behavior
"Admin | Audit Logs | Office 365 Management API Subscription" should give 400 error and "Admin | Audit Logs | Sync Audit Logs (V2)" should complete sucessfully.
What solution are you experiencing the issue with?
Core
What solution version are you using?
4.11
What app or flow are you having the issue with?
Admin | Audit Logs | Sync Audit Logs (V2)
What method are you using to get inventory and telemetry?
Cloud flows
Steps To Reproduce
Anything else?
This the same registration information being used by the Custom Connector for the deprecated solution
The text was updated successfully, but these errors were encountered: