Merge branch 'main' into Viva-chrisda

Author: chrisda

.github/workflows/AutoPublish.yml

@@ -0,0 +1,25 @@
+name: (Scheduled) Publish to live
+
+permissions:
+  contents: write
+  pull-requests: write
+
+on:
+  schedule:
+    - cron: "25 5,11,17,22 * * *" # Times are UTC based on Daylight Saving Time. Need to be adjusted for Standard Time. Scheduling at :25 to account for queuing lag.
+
+  workflow_dispatch:
+
+jobs:
+
+  auto-publish:
+    if: github.repository_owner == 'MicrosoftDocs' && contains(github.event.repository.topics, 'build')
+    uses: MicrosoftDocs/microsoft-365-docs/.github/workflows/Shared-AutoPublish.yml@workflows-prod
+    with:
+        PayloadJson: ${{ toJSON(github) }}
+        EnableAutoPublish: true
+
+    secrets:
+        AccessToken: ${{ secrets.GITHUB_TOKEN }}
+        PrivateKey: ${{ secrets.M365_APP_PRIVATE_KEY }}
+        ClientId: ${{ secrets.M365_APP_CLIENT_ID }}

.github/workflows/StaleBranch.yml

@@ -2,12 +2,17 @@ name: (Scheduled) Stale branch removal
 
 permissions:
   contents: write
-      
+
+# 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.
+# 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.
+# The workflow should not be configured to run after "deletion day" so that users can review the branches were deleted.
+# Recommendation: configure cron to run on days 1,15-31 where 1 is what's configured in 'DeleteOnDayOfMonth'. If 'DeleteOnDayOfMonth' is set to something else, update cron to run the two weeks leading up to it.
+
 on:
   schedule:
-    - cron: "0 9 1 * *"
+    - cron: "0 9 1,15-31 * *"
 
-  # workflow_dispatch:
+  workflow_dispatch:
 
 
 jobs:

exchange/exchange-ps/exchange/New-ManagementScope.md

@@ -406,5 +406,6 @@ To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Ty
 To see the return types, which are also known as output types, that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Output Type field is blank, the cmdlet doesn't return data.
 
 ## NOTES
+Use two-letter country codes (ISO 3166-1 alpha-2) instead of the full country name in filters. For example, use `-RecipientRestrictionFilter "UsageLocation -eq 'FR'"` for France.
 
 ## RELATED LINKS

exchange/exchange-ps/exchange/New-QuarantinePermissions.md

@@ -72,7 +72,7 @@ In the same PowerShell session, you can use `$FullAccess` for the _EndUserQuaran
 ## PARAMETERS
 
 ### -PermissionToAllowSender
-The PermissionToBlockSender parameter specifies whether users are allowed to add the quarantined message sender to their Safe Senders list. Valid values are:
+The PermissionToAllowSender parameter specifies whether users are allowed to add the quarantined message sender to their Safe Senders list. Valid values are:
 
 - $true: Allow sender is available for affected messages in quarantine.
 - $false: Allow sender isn't available for affected messages in quarantine. This is the default value.

exchange/exchange-ps/exchange/Set-AcceptedDomain.md

@@ -307,7 +307,12 @@ Accept wildcard characters: False
 ### -SendingFromDomainDisabled
 This parameter is available only in the cloud-based service.
 
-{{ Fill SendingFromDomainDisabled Description }}
+The SendingFromDomainDisabled parameter specifies whether to allow email to be sent from addresses in the domain. Valid values are:
+
+- $true: Email can't be sent from addresses in the domain.
+- $false: Email can be sent from addresses in the domain.
+
+A common scenario is addresses in a legacy domain that still need to receive email, but shouldn't be used to send email.
 
 ```yaml
 Type: Boolean
@@ -325,7 +330,12 @@ Accept wildcard characters: False
 ### -SendingToDomainDisabled
 This parameter is available only in the cloud-based service.
 
-{{ Fill SendingToDomainDisabled Description }}
+The SendingToDomainDisabled specifies whether to prevent delivery of messages sent to recipients in the domain. Valid values are:
+
+- $true: Email sent to recipients in the domain is blocked.
+- $false: Email sent to recipients in the domain isn't blocked.
+
+A common scenario is to prevent email delivery to recipients in your unused Micorost Online Email Routing Address (MOERA) domain (for example, contoso.onmicrosoft.com).
 
 ```yaml
 Type: Boolean

exchange/exchange-ps/exchange/Set-CASMailbox.md

@@ -502,7 +502,9 @@ Accept wildcard characters: False
 The EwsEnabled parameter enables or disables access to the mailbox using Exchange Web Services clients. Valid values are:
 
 - $true: Access to the mailbox using EWS is enabled. This is the default value.
-- $false: Access to the mailbox using EWS is disabled. The other Exchange Web Services settings in this cmdlet are ignored.
+- $false: Access to the mailbox using EWS is disabled. Other Exchange Web Services settings in this cmdlet are ignored.
+
+The value of this parameter is meaningful only if the EwsEnabled parameter on the Set-OrganizationConfig parameter isn't set to the value $false.
 
 ```yaml
 Type: Boolean
@@ -512,7 +514,7 @@ Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Ex
 
 Required: False
 Position: Named
-Default value: None
+Default value: True
 Accept pipeline input: False
 Accept wildcard characters: False
 ```

exchange/exchange-ps/exchange/Set-MailUser.md

@@ -1569,7 +1569,13 @@ Accept wildcard characters: False
 ### -ExcludeFromAllOrgHolds
 This parameter is available only in the cloud-based service.
 
-{{ Fill ExcludeFromAllOrgHolds Description }}
+The ExcludeFromAllOrgHolds switch specifies whether to exclude the soft-deleted mail user from all organization-wide Microsoft 365 retention policies. You don't need to specify a value with this switch.
+
+When you use this switch, use one of the following values to uniquely identify the soft-deleted mail user in the Identity parameter:
+
+- DistinguishedName
+- Guid
+- ExchangeGuid
 
 ```yaml
 Type: SwitchParameter

exchange/exchange-ps/exchange/Set-ManagementScope.md

@@ -314,5 +314,6 @@ To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Ty
 To see the return types, which are also known as output types, that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Output Type field is blank, the cmdlet doesn't return data.
 
 ## NOTES
+Use two-letter country codes (ISO 3166-1 alpha-2) instead of the full country name in filters. For example, use `-RecipientRestrictionFilter "UsageLocation -eq 'FR'"` for France.
 
 ## RELATED LINKS

teams/teams-ps/teams/Get-CsOnlineUser.md

@@ -320,6 +320,10 @@ A recent fix has addressed an issue where some Guest users were being omitted fr
 - Conferencing_RequiresCommunicationCredits: Allows pay-per minute Audio Conferencing without monthly licenses.
 - CommunicationCredits: Enables users to pay Teams calling and conferencing through the credits.
 
+**Updates in Teams PowerShell Module version 7.0.0 and later**:
+
+- OptionFlags: OptionFlags attribute will no longer be populated with value in the output of Get-CsOnlineUser in all clouds. It's important to note that other details besides EnterpriseVoiceEnabled, previously found in OptionFlags, are no longer relevant for Teams. Administrators can still utilize the EnterpriseVoiceEnabled attribute in the output of the Get-CsOnlineUser cmdlet to get this information. This change will be rolled out to all Teams Powershell Module versions.
+
 **Updates in Teams PowerShell Module version 6.9.0 and later**:
 
 Adds new attribute in the output of Get-CsOnlineUser cmdlet in commercial environments.
@@ -374,8 +378,6 @@ The following updates are applicable for organizations that use Microsoft Teams
 
 - LocationPolicy: LocationPolicy attribute is being deprecated from the output of Get-CsOnlineUser in all clouds. Get-CsPhoneNumberAssignment -IsoCountryCode can be used to get the LocationPolicy information. (Note: LocationPolicy attribute will no longer be populated with value in the older Teams Powershell Module versions (<6.1.0) starting from 20th March 2024.)
 
-- OptionFlags: OptionFlags attribute will no longer be populated with value in the output of Get-CsOnlineUser in all clouds. It's important to note that other details besides EnterpriseVoiceEnabled, previously found in OptionFlags, are no longer relevant for Teams. Administrators can still utilize the EnterpriseVoiceEnabled attribute in the output of the Get-CsOnlineUser cmdlet to get this information. (Note: This change will be rolled out to all Teams Powershell Module versions (=<6.1.0) starting from 20th March 2024.)
-
 **Updates in Teams PowerShell Module version 6.0.0 and later**:
 
 The following updates are applicable for organizations having TeamsOnly users that use Microsoft Teams PowerShell version 6.0.0 or later.

teams/teams-ps/teams/Get-CsPhoneNumberTag.md

@@ -0,0 +1,58 @@
+---
+external help file: Microsoft.Teams.ConfigAPI.Cmdlets-help.xml
+Module Name: Microsoft.Teams.ConfigAPI.Cmdlets
+online version: https://learn.microsoft.com/powershell/module/teams/get-csphonenumbertag
+applicable: Microsoft Teams
+title: Get-CsPhoneNumberTag
+author: pavellatif
+ms.author: pavellatif
+ms.reviewer: pavellatif
+manager: roykuntz
+schema: 2.0.0
+---
+
+# Get-CsPhoneNumberTag
+
+## SYNOPSIS
+This cmdlet allows the admin to get a list of existing tags for telephone numbers.
+
+## SYNTAX
+
+```
+Get-CsPhoneNumberTag [<CommonParameters>]
+```
+
+## DESCRIPTION
+This cmdlet will get a list of all existing tags that are assigned to phone numbers in the tenant. 
+
+## EXAMPLES
+
+### Example 1
+```powershell
+PS C:\> Get-CsPhoneNumberTag
+```
+```output
+TagValue
+HR
+Redmond HQ
+Executives
+```
+
+This example shows how to get a list of existing tags for telephone numbers
+
+## PARAMETERS
+
+### CommonParameters
+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).
+
+## INPUTS
+
+### None
+
+## OUTPUTS
+
+### Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.ISkypeTelephoneNumberMgmtCmdletTenantTagRecord
+
+## NOTES
+
+## RELATED LINKS