Merge pull request #10157 from MicrosoftDocs/chrisda

Formatting and weird character fixes

Author: chrisda

exchange/docs-conceptual/connect-to-exchange-online-protection-powershell.md

@@ -69,7 +69,6 @@ For detailed syntax and parameter information, see [Connect-IPPSSession](/powers
 
 - If you're behind a proxy server, you can use the _PSSessionOption_ parameter in the connection command. First, run this command: `$ProxyOptions = New-PSSessionOption -ProxyAccessType <Value>`, where \<Value\> is `IEConfig`, `WinHttpConfig`, or `AutoDetect`. Then, use the value `$ProxyOptions` for the _PSSessionOption_ parameter. For more information, see [New-PSSessionOption](/powershell/module/microsoft.powershell.core/new-pssessionoption).
 
-
 ### Connect to Security & Compliance PowerShell with an interactive login prompt
 
 This example connects to Exchange Online Protection PowerShell in a Microsoft 365 organization:

exchange/exchange-ps/exchange/Connect-ExchangeOnline.md

@@ -634,7 +634,7 @@ The ShowProgress parameter specifies whether to show or hide the progress bar of
 Type: Boolean
 Parameter Sets: (All)
 Aliases:
-
+Applicable: Exchange Online
 
 Required: False
 Position: Named

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

@@ -12,9 +12,11 @@ ms.reviewer:
 # Set-Label
 
 ## SYNOPSIS
+This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell).
 
 Use the Set-Label cmdlet to modify sensitivity labels in your organization.
 
+For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
 
 ## SYNTAX
 

repo_docs/FAQ.md

@@ -40,24 +40,19 @@ That might be sufficient to meet your communication needs.
 If it doesn't meet your needs, you can use external access policies to extend the ability of your users to communicate and collaborate.
 External access policies can grant (or revoke) the ability of your users to do any or all of the following:
 
-1.
-Communicate with people who have SIP accounts with a federated organization.
+1. Communicate with people who have SIP accounts with a federated organization.
 Note that enabling federation alone will not provide users with this capability.
 Instead, you must enable federation and then assign users an external access policy that gives them the right to communicate with federated users.
 
-2.
-(Microsoft Teams only) Communicate with users who are using custom applications built with [Azure Communication Services (ACS)](/azure/communication-services/concepts/teams-interop). This policy setting only applies if ACS federation has been enabled at the tenant level using the cmdlet [Set-CsTeamsAcsFederationConfiguration](/powershell/module/teams/set-csteamsacsfederationconfiguration).
+2. (Microsoft Teams only) Communicate with users who are using custom applications built with [Azure Communication Services (ACS)](/azure/communication-services/concepts/teams-interop). This policy setting only applies if ACS federation has been enabled at the tenant level using the cmdlet [Set-CsTeamsAcsFederationConfiguration](/powershell/module/teams/set-csteamsacsfederationconfiguration).
 
-3.
-Access Skype for Business Server over the Internet, without having to first log on to your internal network.
+3. Access Skype for Business Server over the Internet, without having to first log on to your internal network.
 This enables your users to use Skype for Business and log on to Skype for Business Server from an Internet café or other remote location.
 
-4.
-Communicate with people who have SIP accounts with a public instant messaging service such as Skype.
+4. Communicate with people who have SIP accounts with a public instant messaging service such as Skype.
 
 The Get-CsExternalAccessPolicy cmdlet provides a way for you to return information about all of the external access policies that have been configured for use in your organization.
 
-
 ## EXAMPLES
 
 ### -------------------------- EXAMPLE 1 --------------------------
@@ -68,7 +63,6 @@ Get-CsExternalAccessPolicy
 Example 1 returns a collection of all the external access policies configured for use in your organization.
 Calling the Get-CsExternalAccessPolicy cmdlet without any additional parameters always returns the complete collection of external access policies.
 
-
 ### -------------------------- EXAMPLE 2 -------------------------- (Skype for Business Online)
 ```
 Get-CsExternalAccessPolicy -Identity "tag:RedmondExternalAccessPolicy"
@@ -77,8 +71,6 @@ Get-CsExternalAccessPolicy -Identity "tag:RedmondExternalAccessPolicy"
 Example 2 uses the Identity parameter to return the external access policy that has the Identity tag:RedmondExternalAccessPolicy.
 Because access policy Identities must be unique, this command will never return more than one item.
 
-
-
 ### -------------------------- EXAMPLE 2 -------------------------- (Skype for Business Server 2015)
 ```
 Get-CsExternalAccessPolicy -Identity site:Redmond
@@ -125,7 +117,6 @@ NOTE: The ApplicableTo parameter can only be used with Skype for Business Online
 
 NOTE: This command requires the Office 365 UsageLocation property to be configured for the user's Active Directory user account.
 
-
 ## PARAMETERS
 
 ### -Identity
@@ -157,18 +148,16 @@ Accept wildcard characters: False
 **Below Content Applies To:** Lync Server 2010, Lync Server 2013, Skype for Business Server 2015
 
 Enables you to do a wildcard search for external access policies.
-For example, to find all the policies configured at the site scope, use this Filter: 
+For example, to find all the policies configured at the site scope, use this Filter:
 
 `site:*`
 
-To find the per-user policies Seattle, Seville, and Saskatoon (all of which start with the letter "S") use this Filter: 
+To find the per-user policies Seattle, Seville, and Saskatoon (all of which start with the letter "S") use this Filter:
 
 `"S*".`
 
 Note that the Filter parameter can only be applied to the policy Identity.
 
-
-
 **Below Content Applies To:** Skype for Business Online
 
 Enables you to do a wildcard search for external access policies.
@@ -182,8 +171,6 @@ To find the per-user policies Seattle, Seville, and Saskatoon (all of which star
 
 Note that the Filter parameter can only be applied to the policy Identity.
 
-
-
 ```yaml
 Type: String
 Parameter Sets: Filter, (All)
@@ -277,20 +264,16 @@ Accept wildcard characters: False
 ### 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 (https://go.microsoft.com/fwlink/?LinkID=113216).
 
-
 ## INPUTS
 
 ### None
 
-
 ## OUTPUTS
 
 ### Microsoft.Rtc.Management.WritableConfig.Policy.ExternalAccess.ExternalAccessPolicy
 
-
 ## NOTES
 
-
 ## RELATED LINKS
 
 [Grant-CsExternalAccessPolicy](Grant-CsExternalAccessPolicy.md)

skype/skype-ps/skype/Get-CsExternalAccessPolicy.md

@@ -111,13 +111,13 @@ Example 6 returns information for user accounts that are categorized as resource
 ## PARAMETERS
 
 ### -AccountType
-This parameter is added to Get-CsOnlineUser starting from TPM 4.5.1 to indicate the user type. The possible values for the AccountType parameter are: 
+This parameter is added to Get-CsOnlineUser starting from TPM 4.5.1 to indicate the user type. The possible values for the AccountType parameter are:
+
 - `User` - to query for user accounts.
 - `ResourceAccount` - to query for app endpoints or resource accounts.
 - `Guest` - to query for guest accounts.
 - `Unknown` - to query for a user type that is not known.
 
-
 ```yaml
 Type: UserIdParameter
 Parameter Sets: (All)
@@ -136,7 +136,6 @@ Indicates the Identity of the user account to be retrieved.
 
 For TeamsOnly customers using the Teams PowerShell Module version 3.0.0 or later, you use the following values to identify the account (note that these changes are currently only rolled out in commercial environments and are currently **not** applicable to government environments):
 
-
 - GUID
 - SIP address
 - UPN
@@ -458,7 +457,7 @@ Accept wildcard characters: False
 ```
 
 ### 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(https://go.microsoft.com/fwlink/?LinkID=113216).
+This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see [about_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216).
 
 ## OUTPUTS
 
@@ -468,7 +467,8 @@ The following updates are applicable for organizations having TeamsOnly users th
 
 *New user attributes*:
 
-FeatureTypes – Array of unique strings specifying what features are enabled for a user. This attribute is an alternatitive to several attributes that have been dropped as outlined in the next section.
+FeatureTypes: Array of unique strings specifying what features are enabled for a user. This attribute is an alternative to several attributes that have been dropped as outlined in the next section.
+
 Some of the commonly used FeatureTypes include:
 
 - Teams
@@ -592,8 +592,8 @@ The following attributes are no longer relevant to Teams and have been dropped f
 - WindowsEmailAddress
 - SoftDeletedUsers (available in Teams PowerShell Module 4.4.3 and later)
 
-
 The following attributes are temporarily unavailable in the output when using the "-Filter" or when used without the "-Identity" parameter:
+
 - WhenChanged
 - CountryAbbreviation
 
@@ -625,7 +625,8 @@ In Teams PowerShell Modules 3.0.0 and above OnPremLineURI will only refer to the
 ## INPUTS
 
 ## NOTES
-- These changes are currently only rolled out in commercial environments and are **not** applicable to government environments.
+
+These changes are currently only rolled out in commercial environments and are **not** applicable to government environments.
 
 ## RELATED LINKS
 

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

@@ -36,19 +36,15 @@ That might be sufficient to meet your communication needs.
 If it doesn't meet your needs you can use external access policies to extend the ability of your users to communicate and collaborate.
 External access policies can grant (or revoke) the ability of your users to do any or all of the following:
 
-1.
-Communicate with people who have SIP accounts with a federated organization.
+1. Communicate with people who have SIP accounts with a federated organization.
 Note that enabling federation will not automatically provide users with this capability.
 Instead, you must enable federation, and then assign users an external access policy that gives them the right to communicate with federated users.
 
-2.
-(Microsoft Teams only) Communicate with users who are using custom applications built with [Azure Communication Services (ACS)](/azure/communication-services/concepts/teams-interop). This policy setting only applies if ACS federation has been enabled at the tenant level using the cmdlet [Set-CsTeamsAcsFederationConfiguration](/powershell/module/teams/set-csteamsacsfederationconfiguration).
+2. (Microsoft Teams only) Communicate with users who are using custom applications built with [Azure Communication Services (ACS)](/azure/communication-services/concepts/teams-interop). This policy setting only applies if ACS federation has been enabled at the tenant level using the cmdlet [Set-CsTeamsAcsFederationConfiguration](/powershell/module/teams/set-csteamsacsfederationconfiguration).
 
-3.
-Communicate with people who have SIP accounts with a public instant messaging service such as Skype.
+3. Communicate with people who have SIP accounts with a public instant messaging service such as Skype.
 
-4.
-Access Skype for Business Server over the Internet, without having to first log on to your internal network.
+4. Access Skype for Business Server over the Internet, without having to first log on to your internal network.
 This enables your users to use Skype for Business and log on to Skype for Business Server from an Internet café or other remote location.
 
 When you install Skype for Business Server, a global external access policy is automatically created for you.
@@ -64,7 +60,6 @@ For example, suppose you create a per-user policy that allows communication with
 As long as that policy is in force, Ken will be allowed to communicate with federated users even if this type of communication is not allowed by Ken's site policy or by the global policy.
 That's because the settings in the per-user policy take precedence.
 
-
 ## EXAMPLES
 
 ### -------------------------- EXAMPLE 1 -------------------------- 
@@ -74,7 +69,6 @@ Grant-CsExternalAccessPolicy -Identity "Ken Myer" -PolicyName RedmondAccessPolic
 
 Example 1 assigns the external access policy RedmondAccessPolicy to the user with the Active Directory display name Ken Myer.
 
-
 ### -------------------------- EXAMPLE 2 -------------------------- 
 ```
 Get-CsUser -LdapFilter "l=Redmond" | Grant-CsExternalAccessPolicy -PolicyName RedmondAccessPolicy
@@ -84,7 +78,6 @@ The command shown in Example 2 assigns the external access policy RedmondAccessP
 To do this, the command first uses the Get-CsUser cmdlet and the LdapFilter parameter to return a collection of all the users who work in Redmond; the filter value "l=Redmond" limits returned data to those users who work in the city of Redmond (the l in the filter, a lowercase L, represents the locality).
 That collection is then piped to the Grant-CsExternalAccessPolicy cmdlet, which assigns the policy RedmondAccessPolicy to each user in the collection.
 
-
 ### -------------------------- EXAMPLE 3 -------------------------- 
 ```
 Get-CsUser -LdapFilter "Title=Sales Representative" | Grant-CsExternalAccessPolicy -PolicyName SalesAccessPolicy
@@ -94,7 +87,6 @@ In Example 3, all the users who have the job title "Sales Representative" are as
 To perform this task, the command first uses the Get-CsUser cmdlet and the LdapFilter parameter to return a collection of all the Sales Representatives; the filter value "Title=Sales Representative" restricts the returned collection to users who have the job title "Sales Representative".
 This filtered collection is then piped to the Grant-CsExternalAccessPolicy cmdlet, which assigns the policy SalesAccessPolicy to each user in the collection.
 
-
 ### -------------------------- EXAMPLE 4 -------------------------- 
 ```
 Get-CsUser -Filter {ExternalAccessPolicy -eq $Null} | Grant-CsExternalAccessPolicy -PolicyName BasicAccessPolicy
@@ -104,7 +96,6 @@ The command shown in Example 4 assigns the external access policy BasicAccessPol
 (That is, users currently being governed by a site policy or by the global policy.) To do this, the Get-CsUser cmdlet and the Filter parameter are used to return the appropriate set of users; the filter value {ExternalAccessPolicy -eq $Null} limits the returned data to user accounts where the ExternalAccessPolicy property is equal to (-eq) a null value ($Null).
 By definition, ExternalAccessPolicy will be null only if users have not been assigned a per-user policy.
 
-
 ### -------------------------- EXAMPLE 5 -------------------------- 
 ```
 Get-CsUser -OU "ou=US,dc=litwareinc,dc=com" | Grant-CsExternalAccessPolicy -PolicyName USAccessPolicy
@@ -114,7 +105,6 @@ Example 5 assigns the external access policy USAccessPolicy to all the users who
 The command starts off by calling the Get-CsUser cmdlet and the OU parameter; the parameter value "ou=US,dc=litwareinc,dc=com" limits the returned data to user accounts found in the US OU.
 The returned collection is then piped to the Grant-CsExternalAccessPolicy cmdlet, which assigns the policy USAccessPolicy to each user in the collection.
 
-
 ### -------------------------- EXAMPLE 6 -------------------------- 
 ```
 Get-CsUser | Grant-CsExternalAccessPolicy -PolicyName $Null
@@ -124,7 +114,6 @@ Example 6 unassigns any per-user external access policy previously assigned to a
 To do this, the command calls the Get-CsUser cmdlet (without any additional parameters) in order to return a collection of all the users enabled for Skype for Business Server.
 That collection is then piped to the Grant-CsExternalAccessPolicy cmdlet, which uses the syntax "`-PolicyName $Null`" to remove any per-user external access policy previously assigned to these users.
 
-
 ## PARAMETERS
 
 ### -Identity