Skip to content

Commit e152215

Browse files
committed
Merge branch 'main' into ICFSA-chrisda
2 parents 4671d68 + 4da0f9e commit e152215

10 files changed

+321
-12
lines changed

exchange/docs-conceptual/exchange-online-powershell-v2.md

Lines changed: 9 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: About the Exchange Online PowerShell V3 module
33
ms.author: chrisda
44
author: chrisda
55
manager: deniseb
6-
ms.date: 06/26/2024
6+
ms.date: 07/16/2024
77
ms.audience: Admin
88
audience: Admin
99
ms.topic: article
@@ -610,14 +610,20 @@ Unless otherwise noted, the current release of the Exchange Online PowerShell mo
610610

611611
### Current release
612612

613+
#### Version 3.5.1
614+
615+
- Bug fixes in **Get-EXOMailboxPermission** and **Get-EXOMailbox**.
616+
- The module has been upgraded to run on .NET 8, replacing the previous version based on .NET 6.
617+
- Enhancements in **Add-VivaModuleFeaturePolicy**.
618+
619+
### Previous releases
620+
613621
#### Version 3.5.0
614622

615623
- New **Get-VivaFeatureCategory** cmdlet.
616624
- Added support for policy operations at the category level in Viva Feature Access Management (VFAM).
617625
- New IsFeatureEnabledByDefault property in the output of **Get-VivaModuleFeaturePolicy**. The value of this property shows the default enablement state for users in the tenant when no tenant or user/group policies were created.
618626

619-
### Previous releases
620-
621627
#### Version 3.4.0
622628

623629
- Bug fixes in **Connect-ExchangeOnline**, **Get-EXORecipientPermission**, and **Get-EXOMailboxFolderPermission**.

exchange/docs-conceptual/whats-new-in-the-exo-module.md

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: What's new in the Exchange Online PowerShell module
33
ms.author: chrisda
44
author: chrisda
55
manager: deniseb
6-
ms.date: 05/17/2024
6+
ms.date: 07/16/2024
77
ms.audience: Admin
88
audience: Admin
99
ms.topic: article
@@ -22,6 +22,12 @@ description: "Learn about the new features and functionality available in the la
2222

2323
This article lists new features in the Exchange Online PowerShell module that's used for connecting to Exchange Online PowerShell, Security & Compliance PowerShell, and standalone Exchange Online Protection (EOP) PowerShell. Features that are currently in preview are denoted with **(preview)**.
2424

25+
## July 2024
26+
27+
- [Version 3.5.1](https://www.powershellgallery.com/packages/ExchangeOnlineManagement/3.5.1) has been released.
28+
29+
For information about what's in this release, see [Version 3.5.1](exchange-online-powershell-v2.md#version-351)
30+
2531
## May 2024
2632

2733
- [Version 3.5.0](https://www.powershellgallery.com/packages/ExchangeOnlineManagement/3.5.0) has been released.

exchange/exchange-ps/exchange/New-Label.md

Lines changed: 47 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -37,6 +37,7 @@ New-Label [-Name] <String> -DisplayName <String> -Tooltip <String>
3737
[-ApplyContentMarkingHeaderFontSize <System.Int32>]
3838
[-ApplyContentMarkingHeaderMargin <System.Int32>]
3939
[-ApplyContentMarkingHeaderText <String>]
40+
[-ApplyDynamicWatermarkingEnabled <System.Boolean>]
4041
[-ApplyWaterMarkingEnabled <System.Boolean>]
4142
[-ApplyWaterMarkingFontColor <String>]
4243
[-ApplyWaterMarkingFontName <String>]
@@ -49,6 +50,7 @@ New-Label [-Name] <String> -DisplayName <String> -Tooltip <String>
4950
[-Confirm]
5051
[-ContentType <MipLabelContentType>]
5152
[-DefaultContentLabel <String>]
53+
[-DynamicWatermarkDisplay <String>]
5254
[-EncryptionAipTemplateScopes <String>]
5355
[-EncryptionContentExpiredOnDateInDaysOrNever <String>]
5456
[-EncryptionDoNotForward <System.Boolean>]
@@ -470,6 +472,29 @@ Accept pipeline input: False
470472
Accept wildcard characters: False
471473
```
472474

475+
### -ApplyDynamicWatermarkingEnabled
476+
**Note**: This parameter is currently in Public Preview, isn't available in all organizations, and is subject to change.
477+
478+
The ApplyDynamicWatermarkingEnabled parameter enables dynamic watermarking for a specific label that applies encryption. Valid values are:
479+
480+
- $true: Enables dynamic watermarking for a specific label.
481+
- $false: Disables dynamic watermarking for a specific label.
482+
483+
You set the watermark text with the DynamicWatermarkDisplay parameter. For more information about using dynamic watermarks for supported apps, see [Dynamic watermarks](https://learn.microsoft.com/purview/encryption-sensitivity-labels#dynamic-watermarks).
484+
485+
```yaml
486+
Type: System.Boolean
487+
Parameter Sets: (All)
488+
Aliases:
489+
Applicable: Security & Compliance
490+
491+
Required: False
492+
Position: Named
493+
Default value: None
494+
Accept pipeline input: False
495+
Accept wildcard characters: False
496+
```
497+
473498
### -ApplyWaterMarkingEnabled
474499
The ApplyWaterMarkingEnabled parameter enables or disables the Apply Watermarking Header action for the label. Valid values are:
475500

@@ -691,6 +716,28 @@ Accept pipeline input: False
691716
Accept wildcard characters: False
692717
```
693718

719+
### -DynamicWatermarkDisplay
720+
**Note**: This parameter is currently in Public Preview, isn't available in all organizations, and is subject to change.
721+
722+
The DynamicWatermarkDisplay parameter specifies the watermark text to display for a given label. This parameter supports text and the following special tokens:
723+
724+
- `${Consumer.PrincipalName}`: Required. The value is the user principal name (UPN) of the user.
725+
726+
This parameter is meaningful only when the ApplyDynamicWatermarkingEnabled parameter value is $true.
727+
728+
```yaml
729+
Type: String
730+
Parameter Sets: (All)
731+
Aliases:
732+
Applicable: Security & Compliance
733+
734+
Required: False
735+
Position: Named
736+
Default value: None
737+
Accept pipeline input: False
738+
Accept wildcard characters: False
739+
```
740+
694741
### -EncryptionAipTemplateScopes
695742
The EncryptionAipTemplateScopes parameter specifies that the label is still published and usable in the AIP classic client. An example value is `"['[email protected]','[email protected]']"`.
696743

exchange/exchange-ps/exchange/Set-Label.md

Lines changed: 47 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -37,6 +37,7 @@ Set-Label [-Identity] <ComplianceRuleIdParameter>
3737
[-ApplyContentMarkingHeaderFontSize <System.Int32>]
3838
[-ApplyContentMarkingHeaderMargin <System.Int32>]
3939
[-ApplyContentMarkingHeaderText <String>]
40+
[-ApplyDynamicWatermarkingEnabled <System.Boolean>]
4041
[-ApplyWaterMarkingEnabled <System.Boolean>]
4142
[-ApplyWaterMarkingFontColor <String>]
4243
[-ApplyWaterMarkingFontName <String>]
@@ -50,6 +51,7 @@ Set-Label [-Identity] <ComplianceRuleIdParameter>
5051
[-ContentType <MipLabelContentType>]
5152
[-DefaultContentLabel <String>]
5253
[-DisplayName <String>]
54+
[-DynamicWatermarkDisplay <String>]
5355
[-EncryptionContentExpiredOnDateInDaysOrNever <String>]
5456
[-EncryptionDoNotForward <System.Boolean>]
5557
[-EncryptionDoubleKeyEncryptionUrl <String>]
@@ -452,6 +454,29 @@ Accept pipeline input: False
452454
Accept wildcard characters: False
453455
```
454456

457+
### -ApplyDynamicWatermarkingEnabled
458+
**Note**: This parameter is currently in Public Preview, isn't available in all organizations, and is subject to change.
459+
460+
The ApplyDynamicWatermarkingEnabled parameter enables dynamic watermarking for a specific label that applies encryption. Valid values are:
461+
462+
- $true: Enables dynamic watermarking for a specific label.
463+
- $false: Disables dynamic watermarking for a specific label.
464+
465+
You set the watermark text with the DynamicWatermarkDisplay parameter. For more information about using dynamic watermarks for supported apps, see [Dynamic watermarks](https://learn.microsoft.com/purview/encryption-sensitivity-labels#dynamic-watermarks).
466+
467+
```yaml
468+
Type: System.Boolean
469+
Parameter Sets: (All)
470+
Aliases:
471+
Applicable: Security & Compliance
472+
473+
Required: False
474+
Position: Named
475+
Default value: None
476+
Accept pipeline input: False
477+
Accept wildcard characters: False
478+
```
479+
455480
### -ApplyWaterMarkingEnabled
456481
The ApplyWaterMarkingEnabled parameter enables or disables the Apply Watermarking Header action for the label. Valid values are:
457482

@@ -689,6 +714,28 @@ Accept pipeline input: False
689714
Accept wildcard characters: False
690715
```
691716

717+
### -DynamicWatermarkDisplay
718+
**Note**: This parameter is currently in Public Preview, isn't available in all organizations, and is subject to change.
719+
720+
The DynamicWatermarkDisplay parameter specifies the watermark text to display for a given label. This parameter supports text and the following special tokens:
721+
722+
- `${Consumer.PrincipalName}`: Required. The value is the user principal name (UPN) of the user.
723+
724+
This parameter is meaningful only when the ApplyDynamicWatermarkingEnabled parameter value is $true.
725+
726+
```yaml
727+
Type: String
728+
Parameter Sets: (All)
729+
Aliases:
730+
Applicable: Security & Compliance
731+
732+
Required: False
733+
Position: Named
734+
Default value: None
735+
Accept pipeline input: False
736+
Accept wildcard characters: False
737+
```
738+
692739
### -EncryptionContentExpiredOnDateInDaysOrNever
693740
The EncryptionContentExpiredOnDateInDaysOrNever parameter specifies when the encrypted content expires. Valid values are:
694741

exchange/exchange-ps/exchange/Set-OrganizationConfig.md

Lines changed: 8 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -3109,16 +3109,18 @@ Accept wildcard characters: False
31093109
### -PostponeRoamingSignaturesUntilLater
31103110
This parameter is available only in the cloud-based service.
31113111

3112-
**Note**: This parameter is in the process of being rolled out. The rollout is expected to be completed by mid-November 2023.
3113-
31143112
The PostponeRoamingSignaturesUntilLater parameter controls whether roaming signatures are enabled or disabled in Outlook on the web (formerly known as Outlook Web App or OWA) and the new Outlook for Windows. Valid values are:
31153113

3116-
- $true: Roaming signatures are temporarily disabled for Outlook on the web and the new Outlook for Windows. For Windows, the registry setting to disable roaming signatures still works. For more information, see [Outlook roaming signatures](https://support.microsoft.com/office/420c2995-1f57-4291-9004-8f6f97c54d15). When roaming signatures are disabled, admins can use the signature-related parameters on the Set-MailboxMessageConfiguration cmdlet (for example, AutoAddSignature, AutoAddSignatureOnReply, and SignatureHtml) to configure email signatures.
3117-
- $false: This is the default value.
3114+
- $true: Roaming signatures are disabled for Outlook on the web and the new Outlook for Windows. For Windows clients, the registry setting to disable roaming signatures still works. For more information, see [Outlook roaming signatures](https://support.microsoft.com/office/420c2995-1f57-4291-9004-8f6f97c54d15). When roaming signatures are disabled, admins can use the signature-related parameters on the Set-MailboxMessageConfiguration cmdlet (for example, AutoAddSignature, AutoAddSignatureOnReply, and SignatureHtml) to configure email signatures.
3115+
3116+
Previously, the only way to disable roaming signatures in Outlook on the web was to open a support ticket. With the introduction of this parameter and value, admins can disable roaming signatures themselves.
3117+
3118+
- $false: Roaming signatures are enabled for Outlook on the web and the new Outlook for Windows. This is the default value.
31183119

3119-
We're working on API support so admins and ISVs can configure roaming signatures directly. When the new API is available (and after plenty of warning), this parameter will be deprecated. Admins will no longer need to disable roaming signatures or use the parameters on Set-MailboxMessageConfiguration to configure email signatures in Outlook on the web.
3120+
We recommend that independent software vendors (ISVs) onboard to the [signature API](https:///javascript/api/outlook/office.body?view=outlook-js-preview#outlook-office-body-setsignatureasync-member(1) based on [event-based hooks
3121+
](/office/dev/add-ins/outlook/autolaunch).
31203122

3121-
Previously, the only way to disable roaming signatures in Outlook on the web was to open a support ticket. With the introduction of this parameter, that process is discontinued as admins can now use this parameter to disable roaming signatures themselves.
3123+
We have no plans to support roaming signature management in the Microsoft Graph API.
31223124

31233125
```yaml
31243126
Type: Boolean
Lines changed: 122 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,122 @@
1+
---
2+
external help file: Microsoft.Teams.ConfigAPI.Cmdlets-help.xml
3+
Module Name: Microsoft.Teams.ConfigAPI.Cmdlets
4+
online version: https://learn.microsoft.com/powershell/module/teams/export-csacquiredphonenumber
5+
applicable: Microsoft Teams
6+
title: Export-CsAcquiredPhoneNumber
7+
author: pavellatif
8+
ms.author: pavellatif
9+
ms.reviewer:
10+
manager: roykuntz
11+
schema: 2.0.0
12+
---
13+
14+
# Export-CsAcquiredPhoneNumber
15+
16+
## SYNOPSIS
17+
This cmdlet exports the list of phone numbers acquired by Teams Phone tenant.
18+
19+
## SYNTAX
20+
21+
```
22+
Export-CsAcquiredPhoneNumber [-Property <String>]
23+
```
24+
25+
## DESCRIPTION
26+
This cmdlet exports all the acquired phone numbers by the tenant to a file. The cmdlet is an asynchronus operation and will return an OrderId. [Get-CsExportAcquiredPhoneNumberStatus](Get-CsExportAcquiredPhoneNumberStatus.md) cmdlet can be used to check the status of the OrderId including the download link to exported file.
27+
28+
By default, this cmdlet returns all the phone numbers acquired by the tenant with all corresponding properties in the results. The tenant admin may indicate specific properties as an input to get a list with only selected properties in the file.
29+
30+
**Available properties to use are: **
31+
32+
- TelephoneNumber
33+
- OperatorId
34+
- NumberType
35+
- LocationId
36+
- CivicAddressId
37+
- NetworkSiteId
38+
- AvailableCapabilities
39+
- AcquiredCapabilities
40+
- BlockId
41+
- RangeId
42+
- AssignmentStatus
43+
- PlaceName
44+
- ActivationState
45+
- PartnerName
46+
- IsOperatorConnect
47+
- IsoCountryCode
48+
- PortInOrderStatus
49+
- DsuSupported
50+
- CapabilityUpdateSupported
51+
- LocationUpdateSupported
52+
- AcquisitionDate
53+
- TargetId
54+
- TargetType
55+
- AssignmentCategory
56+
- SmsCampaignBriefs
57+
- CallingProfileId
58+
- IsoSubdivisionCode
59+
- NumberSource
60+
- ResourceAccountSharedCallingPolicySupported
61+
- SupportedCustomerActions
62+
- ReverseNumberLookup
63+
- RoutingOptions
64+
65+
66+
67+
## EXAMPLES
68+
69+
### Example 1
70+
```powershell
71+
Export-CsAcquiredPhoneNumber
72+
```
73+
```output
74+
OrderId : 0e923e2c-ab0e-4b7a-be5a-906be8c
75+
```
76+
This example displays the OrderId of the export acquired phone numbers operation. The OrderId can be used to get the download link for the file.
77+
78+
### Example 2
79+
```powershell
80+
Export-CsAcquiredPhoneNumber -Property "TelephoneNumber, NumberType, AssignmentStatus"
81+
```
82+
```output
83+
OrderId : 0e923e2c-ab0e-6h8c-be5a-906be8c
84+
```
85+
This example displays the OrderId of the export acquired phone numbers operation. This file will only contain the properties indicated.
86+
87+
## PARAMETERS
88+
89+
### -Property
90+
{{ Fill Property Description }}
91+
92+
```yaml
93+
Type: String
94+
Parameter Sets: (All)
95+
Aliases:
96+
97+
Required: False
98+
Position: Named
99+
Default value: None
100+
Accept pipeline input: False
101+
Accept wildcard characters: False
102+
```
103+
104+
105+
### CommonParameters
106+
This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see [about_CommonParameters](http://go.microsoft.com/fwlink/?LinkID=113216).
107+
108+
## INPUTS
109+
110+
### None
111+
112+
## OUTPUTS
113+
114+
### System.String
115+
116+
## NOTES
117+
The cmdlet is available in Teams PowerShell module 6.1.0 or later.
118+
119+
The cmdlet is only available in commercial and GCC cloud instances.
120+
121+
## RELATED LINKS
122+
[Get-CsExportAcquiredPhoneNumberStatus](Get-CsExportAcquiredPhoneNumberStatus.md)

0 commit comments

Comments
 (0)