msgraph-sdk-dotnet icon indicating copy to clipboard operation
msgraph-sdk-dotnet copied to clipboard

Beta endpoint returns 400

Open goddard82 opened this issue 2 months ago • 3 comments

Describe the bug

The graph API beta endpoint https://graph.microsoft.com/v1.0/reports/authenticationMethods/userMfaSignInSummary does not work and returns a 400 status code.

Expected behavior

The endpoint should return the expected list of userMfaSignInSummary objects.

How to reproduce

In any API client, send a valid GET request to https://graph.microsoft.com/v1.0/reports/authenticationMethods/userMfaSignInSummary with a valid bearer token

SDK Version

No response

Latest version known to work for scenario above?

No response

Known Workarounds

No response

Debug output

Click to expand log ```
</details>


### Configuration

_No response_

### Other information

Example response:

{
	"error": {
		"code": "BadRequest",
		"message": "Resource not found for the segment 'userMfaSignInSummary'.",
		"innerError": {
			"date": "2025-11-05T14:57:50",
			"request-id": "ce41987d-3c95-4f1b-b27a-8126314b5de4",
			"client-request-id": "ce41987d-3c95-4f1b-b27a-8126314b5de4"
		}
	}
}

goddard82 avatar Nov 05 '25 15:11 goddard82

Hi @goddard82, the endpoint is available only in beta version and you called v1.0.

Change https://graph.microsoft.com/v1.0/reports/authenticationMethods/userMfaSignInSummary to https://graph.microsoft.com/beta/reports/authenticationMethods/userMfaSignInSummary

MartinM85 avatar Nov 07 '25 06:11 MartinM85

@MartinM85 Apologies - my mistake. The /beta version returns a 500:

{
	"error": {
		"code": "UnknownError",
		"message": "Please try again after some time. CorrelationId: 2c777d9f-ea05-41ca-849d-0c423322a680",
		"innerError": {
			"date": "2025-11-12T10:10:20",
			"request-id": "d8644e81-0fc3-4257-8992-7e8c0c387590",
			"client-request-id": "d8644e81-0fc3-4257-8992-7e8c0c387590"
		}
	}

}

goddard82 avatar Nov 12 '25 10:11 goddard82

@goddard82 I have the same problem. It takes a really long time to get a response and then it throws a 500 Internal Server Error.

MartinM85 avatar Nov 12 '25 10:11 MartinM85