Skip to content

Commit 7e3d61e

Browse files
American-DipperAmerican-Dipper
authored
Merge branch 'main' into patch-1
2 parents dc6fd35 + 9c2a11b commit 7e3d61e

File tree

6 files changed

+222
-10
lines changed

6 files changed

+222
-10
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/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://learn.microsoft.com/javascript/api/outlook/office.body#outlook-office-body-setsignatureasync-member(1)) based on [event-based hooks
3121+
](https://learn.microsoft.com/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

‎teams/teams-ps/teams/Export-CsAcquiredPhoneNumber.md

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)

‎teams/teams-ps/teams/Get-CsExportAcquiredPhoneNumberStatus.md

Lines changed: 74 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,74 @@
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/get-csexportacquiredphonenumberstatus
5+
applicable: Microsoft Teams
6+
title: Get-CsExportAcquiredPhoneNumberStatus
7+
author: pavellatif
8+
ms.author: pavellatif
9+
ms.reviewer:
10+
manager: roykuntz
11+
schema: 2.0.0
12+
---
13+
14+
# Get-CsExportAcquiredPhoneNumberStatus
15+
16+
## SYNOPSIS
17+
This cmdlet shows the status of the Export-CsAcquiredPhoneNumber cmdlet.
18+
19+
## SYNTAX
20+
21+
### Get-CsExportAcquiredPhoneNumberStatus (Default)
22+
```
23+
Get-CsExportAcquiredPhoneNumberStatus -OrderId <String>
24+
```
25+
26+
## DESCRIPTION
27+
This cmdlet returns the status of the [Export-CsAcquiredPhoneNumber](Export-CsAcquiredPhoneNumber.md) operation. The response will include the download link to the file if operation has been completed.
28+
29+
By Default the download link will remain active for 1 hour.
30+
31+
## EXAMPLES
32+
33+
### Example 1
34+
```powershell
35+
Get-CsExportAcquiredPhoneNumberStatus -OrderId 0e923e2c-ab0e-4b7a-be5a-906be8c
36+
```
37+
38+
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.
39+
40+
## PARAMETERS
41+
42+
### -OrderId
43+
The orderId of the ExportAcquiredNumberStatus cmdlet.
44+
45+
```yaml
46+
Type: String
47+
Parameter Sets: Get
48+
Aliases:
49+
50+
Required: True
51+
Position: Named
52+
Default value: None
53+
Accept pipeline input: False
54+
Accept wildcard characters: False
55+
```
56+
57+
### CommonParameters
58+
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).
59+
60+
## INPUTS
61+
62+
### Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.IConfigApiBasedCmdletsIdentity
63+
64+
## OUTPUTS
65+
66+
### Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.ISkypeTelephoneNumberMgmtGetExportAcquiredTelephoneNumbersResponse
67+
68+
## NOTES
69+
The cmdlet is available in Teams PowerShell module 6.1.0 or later.
70+
71+
The cmdlet is only available in commercial and GCC cloud instances.
72+
73+
## RELATED LINKS
74+
[Get-CsExportAcquiredPhoneNumberStatus](Get-CsExportAcquiredPhoneNumberStatus.md)

‎teams/teams-ps/teams/teams.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -22,6 +22,7 @@ The following cmdlet references are for Microsoft Teams.
2222
### [Disable-CsTeamsShiftsConnectionErrorReport](Disable-CsTeamsShiftsConnectionErrorReport.md)
2323
### [Disconnect-MicrosoftTeams](Disconnect-MicrosoftTeams.md)
2424
### [Enable-CsOnlineSipDomain](Enable-CsOnlineSipDomain.md)
25+
### [Export-CsAcquiredPhoneNumber](Export-CsAcquiredPhoneNumber.md)
2526
### [Export-CsAutoAttendantHolidays](Export-CsAutoAttendantHolidays.md)
2627
### [export-csonlineaudiofile](export-csonlineaudiofile.md)
2728
### [Find-CsGroup](Find-CsGroup.md)
@@ -42,6 +43,7 @@ The following cmdlet references are for Microsoft Teams.
4243
### [Get-CsCloudCallDataConnection](Get-CsCloudCallDataConnection.md)
4344
### [Get-CsDialPlan](Get-CsDialPlan.md)
4445
### [Get-CsEffectiveTenantDialPlan](Get-CsEffectiveTenantDialPlan.md)
46+
### [Get-CsExportAcquiredPhoneNumberStatus](Get-CsExportAcquiredPhoneNumberStatus.md)
4547
### [Get-CsExternalAccessPolicy](Get-CsExternalAccessPolicy.md)
4648
### [Get-CsGroupPolicyAssignment](Get-CsGroupPolicyAssignment.md)
4749
### [Get-CsHybridTelephoneNumber](Get-CsHybridTelephoneNumber.md)

0 commit comments

Comments
 (0)