We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
There are several auto-generated cmdlets associated with the AuditLogQuery API which need to be removed. List as follows: https://learn.microsoft.com/en-us/powershell/module/microsoft.graph.beta.security/get-mgbetasecurityauditlog?view=graph-powershell-beta https://learn.microsoft.com/en-us/powershell/module/microsoft.graph.beta.security/get-mgbetasecurityauditlogquery?view=graph-powershell-beta https://learn.microsoft.com/en-us/powershell/module/microsoft.graph.beta.security/get-mgbetasecurityauditlogquerycount?view=graph-powershell-beta https://learn.microsoft.com/en-us/powershell/module/microsoft.graph.beta.security/get-mgbetasecurityauditlogqueryrecord?view=graph-powershell-beta https://learn.microsoft.com/en-us/powershell/module/microsoft.graph.beta.security/get-mgbetasecurityauditlogqueryrecordcount?view=graph-powershell-beta
We want customers to use the main AuditLogQuery API methods as listed here: https://learn.microsoft.com/en-us/graph/api/resources/security-auditlogquery?view=graph-rest-beta. These auto-generated cmdlets are not actively supported by us and cause confusion/issues among customers.
Removal of cmdlets and associated documentation from public docs.
No response
</details> ### Configuration _No response_ ### Other information _No response_
The text was updated successfully, but these errors were encountered:
timayabi2020
Successfully merging a pull request may close this issue.
Describe the bug
There are several auto-generated cmdlets associated with the AuditLogQuery API which need to be removed. List as follows:
https://learn.microsoft.com/en-us/powershell/module/microsoft.graph.beta.security/get-mgbetasecurityauditlog?view=graph-powershell-beta
https://learn.microsoft.com/en-us/powershell/module/microsoft.graph.beta.security/get-mgbetasecurityauditlogquery?view=graph-powershell-beta
https://learn.microsoft.com/en-us/powershell/module/microsoft.graph.beta.security/get-mgbetasecurityauditlogquerycount?view=graph-powershell-beta
https://learn.microsoft.com/en-us/powershell/module/microsoft.graph.beta.security/get-mgbetasecurityauditlogqueryrecord?view=graph-powershell-beta
https://learn.microsoft.com/en-us/powershell/module/microsoft.graph.beta.security/get-mgbetasecurityauditlogqueryrecordcount?view=graph-powershell-beta
Expected behavior
We want customers to use the main AuditLogQuery API methods as listed here: https://learn.microsoft.com/en-us/graph/api/resources/security-auditlogquery?view=graph-rest-beta.
These auto-generated cmdlets are not actively supported by us and cause confusion/issues among customers.
How to reproduce
Removal of cmdlets and associated documentation from public docs.
SDK Version
No response
Latest version known to work for scenario above?
No response
Known Workarounds
No response
Debug output
Click to expand log
```The text was updated successfully, but these errors were encountered: