Merge pull request MicrosoftDocs#9056 from MicrosoftDocs/chrisda

Chrisda to Master

Author: chrisda

skype/skype-ps/skype/Add-CsSlaDelegates.md

@@ -63,16 +63,12 @@ Accept wildcard characters: False
 ### -Identity
 Indicates the identity of the shared number to which the delegate will be added. 
 User identities can be specified using one of five formats:
-- SIP address
-  - Example: sip:[email protected]
-- User principal name (UPN)
-  - Example: [email protected]
-- Domain name and logon name in the form domain\logon
-  - Example: litwareinc\kenmyer
-- Active Directory display name (this form typically requires quotes)
-  - Example: "Ken Myer"
-- Active Directory distinguished name
-  - Example: CN=KenMyer,CN=Users,DC=Atlanta,DC=Corp,DC=litware,DC=com
+
+- SIP address: Example. sip:[email protected].
+- User principal name (UPN). Example: [email protected].
+- Domain name and logon name in the form domain\logon. Example: litwareinc\kenmyer.
+- Active Directory display name (this form typically requires quotes). Example: "Ken Myer".
+- Active Directory distinguished name. Example: CN=KenMyer,CN=Users,DC=Atlanta,DC=Corp,DC=litware,DC=com
 
 ```yaml
 Type: UserIdParameter

skype/skype-ps/skype/Export-CsAutoAttendantHolidays.md

@@ -27,14 +27,17 @@ The Export-CsAutoAttendantHolidays cmdlet and the Import-CsAutoAttendantHolidays
 The Export-CsAutoAttendantHolidays cmdlet returns the holiday schedule information in serialized form (as a byte array). The caller can then write the bytes to the disk to obtain a CSV file. Similarly, the Import-CsAutoAttendantHolidays cmdlet accepts the holiday schedule information as a byte array, which can be read from the aforementioned CSV file. The first line of the CSV file is considered a header record and is always ignored.
 
 **NOTE**
-- Each line in the CSV file used by Export-CsAutoAttendantHolidays and Import-CsAutoAttendantHolidays cmdlet should be of the following format:
 
-   `HolidayName,StartDateTime1,EndDateTime1,StartDateTime2,EndDateTime2,...,StartDateTime10,EndDateTime10`
+Each line in the CSV file used by Export-CsAutoAttendantHolidays and Import-CsAutoAttendantHolidays cmdlet should be of the following format:
+
+`HolidayName,StartDateTime1,EndDateTime1,StartDateTime2,EndDateTime2,...,StartDateTime10,EndDateTime10`
+
+where
+
+- HolidayName is the name of the holiday to be imported.
+- StartDateTimeX and EndDateTimeX specify a date/time range for the holiday and are optional. If no date-time ranges are defined, then the holiday is imported without any date/time ranges. They follow the same format as New-CsOnlineDateTimeRange cmdlet.
+- EndDateTimeX is optional. If it is not specified, the end bound of the date time range is set to 00:00 of the day after the start date.
 
-    where
-    - HolidayName is the name of the holiday to be imported.
-    - StartDateTimeX and EndDateTimeX specify a date/time range for the holiday and are optional. If no date-time ranges are defined, then the holiday is imported without any date/time ranges. They follow the same format as New-CsOnlineDateTimeRange cmdlet.
-    - EndDateTimeX is optional. If it is not specified, the end bound of the date time range is set to 00:00 of the day after the start date.
 - The first line of the CSV file is considered a header record and is always ignored by Import-CsAutoAttendantHolidays cmdlet.
 - If the destination auto attendant for the import already contains a call flow or schedule by the same name as one of the holidays being imported, the corresponding CSV record is skipped.
 - For holidays that are successfully imported, a default call flow is created which is configured without any greeting and simply disconnects the call on being executed.

skype/skype-ps/skype/Get-CsOnlineUser.md

@@ -159,7 +159,7 @@ For example, a filter that returns only users who have been enabled for Enterpri
 
 The following updates are applicable for TeamsOnly customers using Microsoft Teams PowerShell version 3.0.0 and above.
 
-*Supported filters* 
+*Supported filters*:
 
 The Filtering functionality has been limited to the following attributes:
 
@@ -216,7 +216,7 @@ The Filtering functionality has been limited to the following attributes:
 - CountryAbbreviation
 - UsageLocation
 
-*Attributes renamed*
+*Attributes renamed*:
 
 - ObjectId renamed to Identity
 - FirstName renamed to GivenName
@@ -225,28 +225,29 @@ The Filtering functionality has been limited to the following attributes:
 - Enabled renamed to IsSipEnabled
 - TeamsBranchSurvivabilityPolicy renamed to TeamsSurvivableBranchAppliancePolicy
 
-*Attributes that have changed in meaning/format*
+*Attributes that have changed in meaning/format*:
 
 **OnPremLineURI**: This attribute previously used to refer to both:
+
 1. LineURI set via OnPrem AD.
 2. Direct Routing numbers assigned to users via Set-CsUser.
 
 In Teams PowerShell Modules 3.0.0 and above OnPremLineURI will only refer to the LineURI set via OnPrem AD. Direct Routing numbers will be available from the LineURI field. Direct Routing Numbers can be distinguished from Calling Plan Numbers by looking at the FeatureTypes attribute.
 
-**- The output format of AssignedPlan and ProvisionedPlan have now changed from XML to JSON array.**
-**- The output format of Policies has now changed from String to JSON type UserPolicyDefinition.**
+- **The output format of AssignedPlan and ProvisionedPlan have now changed from XML to JSON array.**
+- **The output format of Policies has now changed from String to JSON type UserPolicyDefinition.**
 
-*Changes in "-Filter" parameter*
+*Changes in "-Filter" parameter*:
 
-- AssignedPlan filter: The previous format will no longer be supported. Existing filters like `AssignedPlan -eq '<some-xml-string>'` will stop working. This needs to be modified to one of the following formats:
-  - ``AssignedPlan -eq "*MCO"`` Returns all users having an AssignedPlan that ends with MCO
-  - ``AssignedPlan -eq "MCO*" ``  Returns all users having an AssignedPlan that starts with MCO
-  - ``AssignedPlan -eq "*MCO*" ``  Returns all users having an AssignedPlan that contains MCO
+AssignedPlan filter: The previous format will no longer be supported. Existing filters like `AssignedPlan -eq '<some-xml-string>'` will stop working. This needs to be modified to one of the following formats:
 
+- ``AssignedPlan -eq "*MCO"`` Returns all users having an AssignedPlan that ends with MCO
+- ``AssignedPlan -eq "MCO*" ``  Returns all users having an AssignedPlan that starts with MCO
+- ``AssignedPlan -eq "*MCO*" ``  Returns all users having an AssignedPlan that contains MCO
 
-*Dropped Filter operators*
+*Dropped Filter operators*:
 
-The following filter syntaxes are not supported in Teams PowerShell Moduled 3.0.0 and above:
+The following filter syntaxes are not supported in Teams PowerShell Module 3.0.0 and above:
 
 - ``-not (<simple/complex PS filter>)``
 - ``<property> -like '*<text>'``
@@ -272,8 +273,8 @@ Accept wildcard characters: False
 Indicates the Identity of the user account to be retrieved.
 User Identities can be specified using one of the following formats: 1) the user's SIP address; 2) the user's user principal name (UPN); or, 3) the user's Active Directory display name (for example, Ken Myer).
 
-You can use the asterisk ( * ) wildcard character when using the Display Name as the user Identity.
-For example, the Identity "* Smith" returns all the users who have a display name that ends with the string value " Smith". 
+You can use the asterisk ( \* ) wildcard character when using the Display Name as the user Identity.
+For example, the Identity "\* Smith" returns all the users who have a display name that ends with the string value " Smith".
 
 Note that in Microsoft Teams PowerShell Version 2.5.1, using this parameter will cause the Get-CsOnlineUser command to no longer emit deprecated properties as part of the modernization effort.
 

skype/skype-ps/skype/New-CsCallingLineIdentity.md

@@ -51,15 +51,15 @@ This example creates a new Caller ID policy that sets the Caller ID to a specifi
 
 ### -------------------------- Example 3 --------------------------
 ```
-New-CsCallingLineIdentity  -Identity Anonymous -Description "anonymous policy" -CallingIDSubstitute Anonymous -EnableUserOverride $false -BlockIncomingPstnCallerID $true
+New-CsCallingLineIdentity -Identity Anonymous -Description "anonymous policy" -CallingIDSubstitute Anonymous -EnableUserOverride $false -BlockIncomingPstnCallerID $true
 ```
 
 This example creates a new Caller ID policy that blocks the incoming Caller ID.
 
 ### Example 4
 ```
 $ObjId = (Get-CsOnlineApplicationInstance -Identity [email protected]).ObjectId
-New-CsCallingLineIdentity  -Identity DKCQ -CallingIDSubstitute Resource -EnableUserOverride $false -ResourceAccount $ObjId -CompanyName "Contoso"
+New-CsCallingLineIdentity -Identity DKCQ -CallingIDSubstitute Resource -EnableUserOverride $false -ResourceAccount $ObjId -CompanyName "Contoso"
 ```
 
 This example creates a new Caller ID policy that sets the Caller ID to the phone number of the specified resource account and sets the Calling party name to Contoso

skype/skype-ps/skype/New-CsExternalAccessPolicy.md

@@ -84,8 +84,8 @@ Note that this new policy sets both the EnableFederationAccess and the EnableOut
 
 ### -------------------------- Example 2 ------------------------
 ```
-Set-CsExternalAccessPolicy -Identity Global  -EnableAcsFederationAccess $true
-New-CsExternalAccessPolicy -Identity AcsFederationNotAllowed  -EnableAcsFederationAccess $false
+Set-CsExternalAccessPolicy -Identity Global -EnableAcsFederationAccess $true
+New-CsExternalAccessPolicy -Identity AcsFederationNotAllowed -EnableAcsFederationAccess $false
 ```
 
 In this example, the Global policy is updated to allow Teams-ACS federation for all users, then a new external access policy instance is created with Teams-ACS federation disabled and which can then be assigned to selected users for which Team-ACS federation will not be allowed.

skype/skype-ps/skype/New-CsInboundExemptNumberPattern.md

@@ -36,7 +36,7 @@ New-CsInboundExemptNumberPattern [-Tenant <Guid>] -Name <String> [-Enabled <Bool
 ### EXAMPLE 1
 
 ```powershell
-PS C:> New-CsInboundExemptNumberPattern  -Identity "AllowContoso1" -Pattern "^\+?1312555888[2|3]$" -Description "Allow Contoso helpdesk" -Enabled $True
+PS C:> New-CsInboundExemptNumberPattern -Identity "AllowContoso1" -Pattern "^\+?1312555888[2|3]$" -Description "Allow Contoso helpdesk" -Enabled $True
 ```
 
 Creates a new inbound exempt number pattern for the numbers 1 (312) 555-88882 and 1 (312) 555-88883 and enables it

skype/skype-ps/skype/New-CsOnlineDateTimeRange.md

@@ -24,7 +24,8 @@ New-CsOnlineDateTimeRange -Start <String> [-End <String>] [-Tenant <Guid>] [<Com
 ## DESCRIPTION
 The New-CsOnlineDateTimeRange cmdlet creates a new date-time range to be used with the Organizational Auto Attendant (OAA) service. Date time ranges are used to form schedules.
 
-**NOTE**
+**NOTE**:
+
 - The start bound of the range must be less than its end bound.
 - The time part of the range must be aligned with 30/60-minutes boundaries.
 - A date time range bound can only be input in the following formats:

skype/skype-ps/skype/New-CsTeamsUpgradePolicy.md

@@ -38,15 +38,15 @@ Notes:
 ### Example 1: Create a site-level policy
 
 ```powershell
-PS C:\> new-CsTeamsUpgradePolicy -identity site:Redmond1  -NotifySfBUsers $true
+PS C:\> new-CsTeamsUpgradePolicy -identity site:Redmond1 -NotifySfBUsers $true
 ```
 
 This creates a policy for users in the site Redmond1.
 
 ### Example 2: Create a policy not specific to a site.
 
 ```powershell
-PS C:\> new-CsTeamsUpgradePolicy -identity EnableNotifications  -NotifySfBUsers $true
+PS C:\> new-CsTeamsUpgradePolicy -identity EnableNotifications -NotifySfBUsers $true
 ```
 
 This creates a policy for users that can be granted as desired to individual users

skype/skype-ps/skype/Remove-CsSlaDelegates.md

@@ -63,16 +63,12 @@ Accept wildcard characters: False
 
 ### -Identity
 Indicates the identity of the shared number to which the delegate will be removed. User identities can be specified using one of five formats:
-- SIP address
-  - Example: sip:[email protected]
-- User principal name (UPN)
-  - Example: [email protected]
-- Domain name and logon name in the form domain\logon
-  - Example: litwareinc\kenmyer
-- Active Directory display name (this form typically requires quotes)
-  - Example: "Ken Myer"
-- Active Directory distinguished name
-  - Example: CN=KenMyer,CN=Users,DC=Atlanta,DC=Corp,DC=litware,DC=com
+
+- SIP address. Example: sip:[email protected].
+- User principal name (UPN). Example: [email protected].
+- Domain name and logon name in the form domain\logon. Example: litwareinc\kenmyer.
+- Active Directory display name (this form typically requires quotes). Example: "Ken Myer".
+- Active Directory distinguished name. Example: CN=KenMyer,CN=Users,DC=Atlanta,DC=Corp,DC=litware,DC=com.
 
 ```yaml
 Type: UserIdParameter

skype/skype-ps/skype/Set-CsCallingLineIdentity.md

@@ -71,7 +71,7 @@ This example modifies the new Anonymous Caller ID policy that blocks the incomin
 ### Example 4
 ```
 $ObjId = (Get-CsOnlineApplicationInstance -Identity [email protected]).ObjectId
-Set-CsCallingLineIdentity  -Identity DKCQ -CallingIDSubstitute Resource -ResourceAccount $ObjId -CompanyName "Contoso"
+Set-CsCallingLineIdentity -Identity DKCQ -CallingIDSubstitute Resource -ResourceAccount $ObjId -CompanyName "Contoso"
 ```
 
 This example modifies the Caller ID policy that sets the Caller ID to the phone number of the specified resource account and sets the Calling party name to Contoso

skype/skype-ps/skype/Set-CsExternalAccessPolicy.md

@@ -114,16 +114,16 @@ The net result: all external access policies that allow public cloud access will
 
 ### -------------------------- Example 5 ------------------------
 ```
-Set-CsExternalAccessPolicy -Identity Global  -EnableAcsFederationAccess $false
-New-CsExternalAccessPolicy -Identity AcsFederationAllowed  -EnableAcsFederationAccess $true
+Set-CsExternalAccessPolicy -Identity Global -EnableAcsFederationAccess $false
+New-CsExternalAccessPolicy -Identity AcsFederationAllowed -EnableAcsFederationAccess $true
 ```
 
 In this example, the Global policy is updated to disallow Teams-ACS federation for all users, then a new external access policy instance is created with Teams-ACS federation enabled and which can be assigned to selected users for which Team-ACS federation will be allowed.
 
 ### -------------------------- Example 5 ------------------------
 ```
-Set-CsExternalAccessPolicy -Identity Global  -EnableAcsFederationAccess $true
-New-CsExternalAccessPolicy -Identity AcsFederationNotAllowed  -EnableAcsFederationAccess $false
+Set-CsExternalAccessPolicy -Identity Global -EnableAcsFederationAccess $true
+New-CsExternalAccessPolicy -Identity AcsFederationNotAllowed -EnableAcsFederationAccess $false
 ```
 
 In this example, the Global policy is updated to allow Teams-ACS federation for all users, then a new external access policy instance is created with Teams-ACS federation disabled and which can then be assigned to selected users for which Team-ACS federation will not be allowed.

skype/skype-ps/skype/Set-CsInboundExemptNumberPattern.md

@@ -24,15 +24,15 @@ This cmdlet modifies one or more parameters of a exempt number pattern in the te
 ### EXAMPLE 1
 
 ```powershell
-PS C:> Set-CsInboundExemptNumberPattern  -Identity "AllowContoso1" -Pattern "^\+?1312555888[2|3]$"
+PS C:> Set-CsInboundExemptNumberPattern -Identity "AllowContoso1" -Pattern "^\+?1312555888[2|3]$"
 ```
 
 Sets the inbound exempt number pattern for AllowContoso1
 
 ### EXAMPLE 2
 
 ```powershell
-PS C:> Set-CsInboundExemptNumberPattern  -Identity "AllowContoso1" -Enabled $False
+PS C:> Set-CsInboundExemptNumberPattern -Identity "AllowContoso1" -Enabled $False
 ```
 
 Disables the exempt number pattern from usage in call blocking