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

New Command: Create a Purview retention event type #4341

Closed
Tracked by #4145
martinlingstuyl opened this issue Jan 11, 2023 · 3 comments
Closed
Tracked by #4145

New Command: Create a Purview retention event type #4341

martinlingstuyl opened this issue Jan 11, 2023 · 3 comments

Comments

@martinlingstuyl
Copy link
Contributor

martinlingstuyl commented Jan 11, 2023

Usage

m365 purview retentioneventtype add [options]

Description

Create a retention event type

Options

Option Description
-n, --displayName <displayName> The display name of the event type
-d, --description [description] A description for the event type

Examples

Create a retention event type contract expiry event

m365 purview retentioneventtype add --displayName 'contract expiry event' --description 'A retention event type to start a retention period based on the date that a contract expired.'

Additional Info

The following Graph endpoint can be used:
https://graph.microsoft.com/beta/security/triggerTypes/retentionEventTypes

More information

Beta notice

The Graph endpoint that's used is in beta, so we should add a beta notice to the docs.

More information

This section should be included in the documentation

This command is part of a series of commands that have to do with event-based retention. Event-based retention is about starting a retention period when a specific event occurs, instead of the moment a document was labeled or created.

Read more on event-based retention here

@martinlingstuyl martinlingstuyl added good first issue new feature needs peer review Needs second pair of eyes to review the spec or PR and removed needs peer review Needs second pair of eyes to review the spec or PR labels Jan 11, 2023
@Adam-it
Copy link
Contributor

Adam-it commented Jan 21, 2023

nothing to add. @martinlingstuyl looks good 👍

@martinlingstuyl martinlingstuyl added help wanted and removed needs peer review Needs second pair of eyes to review the spec or PR labels Jan 22, 2023
@MathijsVerbeeck
Copy link
Contributor

Pick me!

@milanholemans
Copy link
Contributor

Cool, all yours!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants