-
Notifications
You must be signed in to change notification settings - Fork 490
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Assert-M365DSCBlueprint: export to json and switch to open browser after run #2345
Comments
The json switch sounds interesting. Could you elaborate a bit more about the switch and the use case? AFAIK, Opening something from within Azure Automation is not possible. |
Thank you for the additional information. This helps to better understand your requirement. I just reviewed the function and am very confident that we can add the switch easily.
Adding the json export is something I would need to review. |
Thanks for your quick reply! |
Changed the default behavior not to open the files by default. This is to align it with the New-M365DSCReportFromConfiguration cmdlet. Also added the -Type switch to Assert-M365DSCBlueprint and New-M365DSCDeltaReport to support specifying HTML or JSON |
Fixes #2345 - Support for JSON report in Assert-M365DSCBlueprint
Thanks for the quick action. Works great! |
Description
I would like to use Microsoft 365 DSC in Azure Automation for reporting on deviations. Is it possible to incorporate 2 additional features:
Proposed properties
Special considerations or limitations
The text was updated successfully, but these errors were encountered: