Skip to content
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

Removal of auto-generated cmdlets from AuditLogQuery API #2961

Closed
arishojaswi opened this issue Sep 18, 2024 · 0 comments · Fixed by #2968
Closed

Removal of auto-generated cmdlets from AuditLogQuery API #2961

arishojaswi opened this issue Sep 18, 2024 · 0 comments · Fixed by #2968
Assignees
Labels
type:bug A broken experience

Comments

@arishojaswi
Copy link

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 ```
</details>


### Configuration

_No response_

### Other information

_No response_
@arishojaswi arishojaswi added status:waiting-for-triage An issue that is yet to be reviewed or assigned type:bug A broken experience labels Sep 18, 2024
@timayabi2020 timayabi2020 self-assigned this Sep 23, 2024
@timayabi2020 timayabi2020 removed the status:waiting-for-triage An issue that is yet to be reviewed or assigned label Sep 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:bug A broken experience
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants