Skip to content

Commit 9bc243e

Browse files
chrisdachrisda
authored
Merge pull request MicrosoftDocs#2297 from MicrosoftDocs/chrisda
Update Set-UnifiedGroup.md
2 parents 5785c8e + c70993c commit 9bc243e

File tree

1 file changed

+150
-0
lines changed

1 file changed

+150
-0
lines changed

‎exchange/exchange-ps/exchange/users-and-groups/Set-UnifiedGroup.md

Lines changed: 150 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -61,10 +61,15 @@ Set-UnifiedGroup [-Identity] <UnifiedGroupIdParameter>
6161
[-MailboxRegion <String>]
6262
[-MailTip <String>]
6363
[-MailTipTranslations <MultiValuedProperty>]
64+
[-MaxReceiveSize <Unlimited>]
65+
[-MaxSendSize <Unlimited>]
66+
[-ModeratedBy <MultiValuedProperty>]
67+
[-ModerationEnabled <$true | $false>]
6468
[-Notes <String>]
6569
[-PrimarySmtpAddress <SmtpAddress>]
6670
[-RejectMessagesFromSendersOrMembers <MultiValuedProperty>]
6771
[-RequireSenderAuthenticationEnabled <$true | $false>]
72+
[-SubscriptionEnabled]
6873
[-UnifiedGroupWelcomeMessageEnabled]
6974
[-WhatIf] [<CommonParameters>]
7075
```
@@ -901,6 +906,132 @@ Accept pipeline input: False
901906
Accept wildcard characters: False
902907
```
903908
909+
### -MaxReceiveSize
910+
The MaxReceiveSize parameter specifies the maximum size of an email message that can be sent to this group. Messages that exceed the maximum size are rejected by the group.
911+
912+
When you enter a value, qualify the value with one of the following units:
913+
914+
- B (bytes)
915+
916+
- KB (kilobytes)
917+
918+
- MB (megabytes)
919+
920+
- GB (gigabytes)
921+
922+
- TB (terabytes)
923+
924+
Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
925+
926+
Valid values are from 0 through 2147482624 bytes.
927+
928+
By default, the MaxReceiveSize parameter is set to the value unlimited. This indicates the maximum message size for the group is controlled by other message size limits in the organization.
929+
930+
For any message size limit, you need to set a value that's larger than the actual size you want enforced. This accounts for the Base64 encoding of attachments and other binary data. Base64 encoding increases the size of the message by approximately 33%, so the value you specify should be approximately 33% larger than the actual message size you want enforced. For example, if you specify a maximum message size value of 64 MB, you can expect a realistic maximum message size of approximately 48 MB.
931+
932+
```yaml
933+
Type: Unlimited
934+
Parameter Sets: (All)
935+
Aliases:
936+
Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
937+
Required: False
938+
Position: Named
939+
Default value: None
940+
Accept pipeline input: False
941+
Accept wildcard characters: False
942+
```
943+
944+
### -MaxSendSize
945+
The MaxSendSize parameter specifies the maximum size of an email message that can be sent by this group.
946+
947+
When you enter a value, qualify the value with one of the following units:
948+
949+
- B (bytes)
950+
951+
- KB (kilobytes)
952+
953+
- MB (megabytes)
954+
955+
- GB (gigabytes)
956+
957+
- TB (terabytes)
958+
959+
Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
960+
961+
Valid values are from 0 through 2147482624 bytes.
962+
963+
By default, the MaxSendSize parameter is set to the value unlimited. This indicates the maximum message size for the group is controlled by other message size limits in the organization.
964+
965+
For any message size limit, you need to set a value that's larger than the actual size you want enforced. This accounts for the Base64 encoding of attachments and other binary data. Base64 encoding increases the size of the message by approximately 33%, so the value you specify should be approximately 33% larger than the actual message size you want enforced. For example, if you specify a maximum message size value of 64 MB, you can expect a realistic maximum message size of approximately 48 MB.
966+
967+
```yaml
968+
Type: Unlimited
969+
Parameter Sets: (All)
970+
Aliases:
971+
Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
972+
Required: False
973+
Position: Named
974+
Default value: None
975+
Accept pipeline input: False
976+
Accept wildcard characters: False
977+
```
978+
979+
### -ModeratedBy
980+
The ModeratedBy parameter specifies one or more moderators for this recipient. A moderator approves messages sent to the recipient before the messages are delivered. A moderator must be a mailbox, mail user, or mail contact in your organization. You can use any value that uniquely identifies the moderator.
981+
982+
For example:
983+
984+
- Name
985+
986+
- Display name
987+
988+
- Alias
989+
990+
- Distinguished name (DN)
991+
992+
- Canonical DN
993+
994+
- Email address
995+
996+
- GUID
997+
998+
To enter multiple values, use the following syntax: \<value1\>,\<value2\>,...\<valueX\>. If the values contain spaces or otherwise require quotation marks, use the following syntax: "\<value1\>","\<value2\>",..."\<valueX\>".
999+
1000+
You need to use this parameter to specify at least one moderator when you set the ModerationEnabled parameter to the value $true.
1001+
1002+
```yaml
1003+
Type: MultiValuedProperty
1004+
Parameter Sets: (All)
1005+
Aliases:
1006+
Applicable: Exchange Online
1007+
Required: False
1008+
Position: Named
1009+
Default value: None
1010+
Accept pipeline input: False
1011+
Accept wildcard characters: False
1012+
```
1013+
1014+
### -ModerationEnabled
1015+
The ModerationEnabled parameter specifies whether moderation is enabled for this recipient. Valid value are:
1016+
1017+
- $true: Moderation is enabled for this recipient. Messages sent to this recipient must be approved by a moderator before the messages are delivered.
1018+
1019+
- $false: Moderation is disabled for this recipient. Messages sent to this recipient are delivered without the approval of a moderator. This is the default value.
1020+
1021+
You use the ModeratedBy parameter to specify the moderators.
1022+
1023+
```yaml
1024+
Type: $true | $false
1025+
Parameter Sets: (All)
1026+
Aliases:
1027+
Applicable: Exchange Online
1028+
Required: False
1029+
Position: Named
1030+
Default value: None
1031+
Accept pipeline input: False
1032+
Accept wildcard characters: False
1033+
```
1034+
9041035
### -Notes
9051036
The Notes parameter specifies the description of the Office 365 Group. If the value contains spaces, enclose the value in quotation marks.
9061037
@@ -991,6 +1122,25 @@ Accept pipeline input: False
9911122
Accept wildcard characters: False
9921123
```
9931124
1125+
### -SubscriptionEnabled
1126+
The SubscriptionEnabled switch specifies whether subscriptions to conversations and calendar events are enabled for the Office 365 Group.
1127+
1128+
- To change the value to $true, use this switch without a value.
1129+
-
1130+
- To change the value to $false, use this exact syntax: -SubscriptionEnabled:$false.
1131+
1132+
```yaml
1133+
Type: SwitchParameter
1134+
Parameter Sets: (All)
1135+
Aliases:
1136+
Applicable: Exchange Online
1137+
Required: False
1138+
Position: Named
1139+
Default value: None
1140+
Accept pipeline input: False
1141+
Accept wildcard characters: False
1142+
```
1143+
9941144
### -UnifiedGroupWelcomeMessageEnabled
9951145
The UnifiedGroupWelcomeMessageEnabled switch specifies whether to enable or disable sending system-generated welcome messages to users who are added as members to the Office 365 Group.
9961146

0 commit comments

Comments
 (0)