You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .github/workflows/StaleBranch.yml
+1Lines changed: 1 addition & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -2,6 +2,7 @@ name: (Scheduled) Stale branch removal
2
2
3
3
permissions:
4
4
contents: write
5
+
pull-requests: read
5
6
6
7
# This workflow is designed to be run in the days up to, and including, a "deletion day", specified by 'DeleteOnDayOfMonth' in env: in https://github.com/MicrosoftDocs/microsoft-365-docs/blob/workflows-prod/.github/workflows/Shared-StaleBranch.yml.
7
8
# On the days leading up to "deletion day", the workflow will report the branches to be deleted. This lets users see which branches will be deleted. On "deletion day", those branches are deleted.
\*-AppRetentionCompliance\* cmdlets are used for policies with adaptive policy scopes and all static policies that cover Teams private channels, Viva Engage chats, and Viva Engage community messages. Eventually, you'll use these cmdlets for most retention locations and policy types. The \*-RetentionCompliance\* cmdlets will continue to support Exchange and SharePoint locations primarily. For policies created with the \*-AppRetentionCompliance\* cmdlets, you can only set the list of included or excluded scopes for all included workloads, which means you'll likely need to create one policy per workload.
53
+
\*-AppRetentionCompliance\* cmdlets are used for policies with adaptive policy scopes and all static policies in the locations described in [Retention cmdlets for newer locations](https://learn.microsoft.com/purview/retention-cmdlets#retention-cmdlets-for-newer-locations). You can only set the list of included or excluded scopes for all included workloads, which means you likely need to create one policy per workload.
54
+
55
+
\*-RetentionCompliance\* cmdlets continue to primarily support the locations described in [Retention cmdlets for older locations](https://learn.microsoft.com/purview/retention-cmdlets#retention-cmdlets-for-older-locations).
54
56
55
57
To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions).
- **Other AI apps**: Currently in Preview. You must use *all* of the following values at the same time:
112
132
113
-
This parameter uses the following syntax: `"LocationtType:App1,LocationType:App2,...LocationType:AppN` where LocationType is User or Group. For example, `"User:Exchange,User:OneDriveForBusiness,Group:Exchange,Group:SharePoint"` or `"User:MicrosoftTeams","User:VivaEngage"`.
This parameter is reserved for internal Microsoft use.
90
-
91
-
```yaml
92
-
Type: SwitchParameter
93
-
Parameter Sets: (All)
94
-
Aliases:
95
-
Applicable: Security & Compliance
96
-
97
-
Required: False
98
-
Position: Named
99
-
Default value: None
100
-
Accept pipeline input: False
101
-
Accept wildcard characters: False
102
-
```
103
-
104
-
### -IrmDiscovery
105
-
This parameter is reserved for internal Microsoft use.
106
-
107
-
```yaml
108
-
Type: SwitchParameter
109
-
Parameter Sets: (All)
110
-
Aliases:
111
-
Applicable: Security & Compliance
112
-
113
-
Required: False
114
-
Position: Named
115
-
Default value: None
116
-
Accept pipeline input: False
117
-
Accept wildcard characters: False
118
-
```
119
-
120
86
### -WhatIf
121
87
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
0 commit comments