Repository navigation
Unable to create a configuration snapshot job with ConfigurationManagement builder #3155
Description
Describe the bug
I am trying to create a snapshot to be used for creating a monitor in tenant configuration management api, but getting an AggregateException with 404 code and an empty message. It seems, that no methods are implemented in this builder, as this code produces the exception:
graphClient.Admin.ConfigurationManagement.ConfigurationSnapshot.PostAsync(body)
It seems the correct method should be ConfigurationSnapshot.CreateSnapshot.PostAsync but it just doesn't exist. Also, it accepts the object of the type ConfigurationBaseline however in the Microsoft Graph API docs, the type should be probably something like ConfigurationSnapshotJob, or at least sharing properties with this type
Expected behavior
await graphClient.Admin.ConfigurationManagement.ConfigurationSnapshot.PostAsync(body)
should be scheduling a ConfigurationSnapshotJob and providing it in the response body. Alternatively, the following method should exist to conform with the API schema:
await graphClient.Admin.ConfigurationManagement.ConfigurationSnapshots.CreateSnapshot.PostAsync(body)
How to reproduce
If all permissions are assigned and Graph Service Client is created, just call:
await graphClient.Admin.ConfigurationManagement.ConfigurationSnapshot.PostAsync(body)
SDK Version
6.2.0
Latest version known to work for scenario above?
No response
Known Workarounds
Currently, issuing regular HTTP calls without using SDK works. The documentation also omits the part on C# (dotnet) SDK, it just has the HTTP and Javascript sections:
https://learn.microsoft.com/en-us/graph/api/configurationbaseline-createsnapshot?view=graph-rest-1.0&tabs=http
Debug output
Click to expand log
```Graph API error (HTTP 404)
Code: UnknownError
Message:
</details>
### Configuration
- OS: Ubuntu 24.04 (WSL)
- x64
### Other information
_No response_
Activity
BartRolls commentedon Sep 16, 2026
Thanks for raising this issue, I just ran into it myself.
Since I already have authentication set up on the GraphServiceClient in our library, I use the RequestAdapter to call the API directly. Setting up a fresh HttpClient with token authentication would be quite some work.
Here is the code I use: