Merge pull request #683 from MicrosoftDocs/global-admin-batch-2

Stacyrch140 · web-flow · commit f7cb4e672002 · 2024-09-03T16:57:06.000-04:00
2nd batch of sharepoint powershell global admin mentioning removal
diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOSiteGroup.md b/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOSiteGroup.md
@@ -25,7 +25,7 @@ Set-SPOSiteGroup -Identity <String> [-Name <String>] [-Owner <String>] [-Permiss
 
 ## DESCRIPTION
 
-You must be a SharePoint Online administrator or Global Administrator and be a site collection administrator to run the `Set-SPOSiteGroup` cmdlet.
+You must be at least a SharePoint Online administrator and be a site collection administrator to run the `Set-SPOSiteGroup` cmdlet.
 
 For permissions and the most current information about Windows PowerShell for SharePoint Online, see the online documentation at [Intro to SharePoint Online Management Shell](https://learn.microsoft.com/powershell/sharepoint/sharepoint-online/introduction-sharepoint-online-management-shell?view=sharepoint-ps).
 
diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOSiteOffice365Group.md b/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOSiteOffice365Group.md
@@ -32,7 +32,7 @@ Set-SPOSiteOffice365Group
 
 ## DESCRIPTION
 
-Connects a top-level SPO site collection to a new Microsoft 365 Group. You must be a SharePoint Online administrator or Global administrator to run the cmdlet and be a site collection administrator of the site.
+Connects a top-level SPO site collection to a new Microsoft 365 Group. You must be at least a SharePoint Online administrator to run the cmdlet and be a site collection administrator of the site.
 
 If the site doesn't exist, this cmdlet returns a "File not found" error.
 
diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOTenantRenameSitePrioritization.md b/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOTenantRenameSitePrioritization.md
@@ -28,17 +28,25 @@ It is possible to start prioritizing sites only once the rename operation has be
 
 Please note that prioritizing a site is not a guarantee that it will complete first. There are several factors that can affect processing times, and multiple site renames are processed in parallel. Prioritized sites have a much higher chance of completing first.
 
-You must be a SharePoint or Global Administrator to run this cmdlet.
+You must be at least a SharePoint administrator to run the cmdlet.
+
 ## EXAMPLES
+
 ### Example 1
+
 ```powershell
 Set-SPOTenantRenameSitePrioritization -SiteUrl https://contoso.sharepoint.com/sites/projectx
 ```
-This example prioritizes the 'projectx' site within the Advanced Tenant Rename. 	
+
+This example prioritizes the 'projectx' site within the Advanced Tenant Rename.
+
 ## PARAMETERS
+
 ### -SiteUrl
+
 Specifies the full site URL of the site you wish to prioritize. This can be either a OneDrive for Business or SharePoint Online site. Root URLs (e.g., contoso.sharepoint.com, contoso-admin.sharepoint.com or contoso-my.sharepoint.com) can't be prioritized.
 ```yaml
+
 Type: String
 Parameter Sets: (All)
 Aliases:
@@ -49,12 +57,21 @@ Default value: None
 Accept pipeline input: False
 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](http://go.microsoft.com/fwlink/?LinkID=113216).
+
 ## INPUTS
+
 ### None
+
 ## OUTPUTS
+
 ### System.Object
+
 ## NOTES
+
 ## RELATED LINKS
+
 [Advanced Tenant Rename](https://aka.ms/advancedtenantrename)
diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOTenantSyncClientRestriction.md b/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOTenantSyncClientRestriction.md
@@ -40,7 +40,7 @@ Set-SPOTenantSyncClientRestriction [-ExcludedFileExtensions <String>] [<CommonPa
 
 This cmdlet contains more than one parameter set. You may only use parameters from one parameter set, and you may not combine parameters from different parameter sets. For more information about how to use parameter sets, see [Cmdlet Parameter Sets](https://msdn.microsoft.com/library/dd878348(VS.85).aspx).
 
-You must be a SharePoint Online administrator or Global Administrator to run the cmdlet.
+You must be at least a SharePoint administrator to run the cmdlet.
 
 Requires a valid Connect-SPOService context to identify the tenant. For information on how to connect to the tenant, see [Connect-SPOService](Connect-SPOService.md)
 
diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOUser.md b/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOUser.md
@@ -27,7 +27,7 @@ Set-SPOUser -IsSiteCollectionAdmin <Boolean> -LoginName <String> -Site <SpoSiteP
 Use the `Set-SPOUser` cmdlet to configure properties of an existing user.
 That is, to add or remove a user as a SharePoint Online site collection administrator.
 
-You must have the SharePoint Online Administrator or Global Administrator role to run the cmdlet.
+You must be at least a SharePoint administrator to run the cmdlet.
 
 For permissions and the most current information about Windows PowerShell for SharePoint Online, see the online documentation at [Intro to SharePoint Online Management Shell](https://learn.microsoft.com/powershell/sharepoint/sharepoint-online/introduction-sharepoint-online-management-shell?view=sharepoint-ps).
 
diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Start-SPOUserAndContentMove.md b/sharepoint/sharepoint-ps/sharepoint-online/Start-SPOUserAndContentMove.md
@@ -26,7 +26,7 @@ Start-SPOUserAndContentMove [-UserPrincipalName] <String> [-DestinationDataLocat
 
 ## DESCRIPTION
 
-This cmdlet applies to Multi-Geo tenants and it is designed to move user profiles and their corresponding OneDrive personal sites across geo locations. These cmdlets may only be ran by a SharePoint or Global administrator, who is connected to the SharePoint administration center of the geo location where the user is currently hosted. 
+This cmdlet applies to Multi-Geo tenants and it is designed to move user profiles and their corresponding OneDrive personal sites across geo locations. These cmdlets may only be run by a SharePoint administrator or above, who is connected to the SharePoint administration center of the geo location where the user is currently hosted. 
 
 ## EXAMPLES
 
diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Test-SPOSite.md b/sharepoint/sharepoint-ps/sharepoint-online/Test-SPOSite.md
@@ -28,7 +28,7 @@ The `Test-SPOSite` cmdlet runs one or all site collection health checks on the s
 Tests are intended not to make any changes except in repair mode, which can be initiated by running the `Repair-SPOSite` cmdlet.
 This cmdlet reports the rules together with a summary of the results.
 
-You must be a SharePoint Online administrator or Global Administrator to run the `Test-SPOSite` cmdlet.
+You must be at least a SharePoint administrator to run the cmdlet.
 
 For permissions and the most current information about Windows PowerShell for SharePoint Online, see the online documentation at [Intro to SharePoint Online Management Shell](https://learn.microsoft.com/powershell/sharepoint/sharepoint-online/introduction-sharepoint-online-management-shell?view=sharepoint-ps).
 
diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Unlock-SPOSensitivityLabelEncryptedFile.md b/sharepoint/sharepoint-ps/sharepoint-online/Unlock-SPOSensitivityLabelEncryptedFile.md
@@ -26,7 +26,7 @@ Unlock-SPOSensitivityLabelEncryptedFile -FileUrl <absolute path for file> -Justi
 
 The `Unlock-SPOSensitivityLabelEncryptedFile` cmdlet runs on a single office online file that is encrypted via sensitivity label. It decrypts the file and removes the label from the file.
 
-You must be a SharePoint Online administrator or Global Administrator to run the `Unlock-SPOSensitivityLabelEncryptedFile` cmdlet. This cmdlet doesn't work on files that have double key encryption or files that have encryption but are not processed by SharePoint. These files don't show the name of the label in the Sensitivity column, and you can't edit these files in Office Online.
+You must be at least a SharePoint Online administrator to run the `Unlock-SPOSensitivityLabelEncryptedFile` cmdlet. This cmdlet doesn't work on files that have double key encryption or files that have encryption but are not processed by SharePoint. These files don't show the name of the label in the Sensitivity column, and you can't edit these files in Office Online.
 
 For permissions and the most current information about Windows PowerShell for SharePoint Online, see the online documentation at [Intro to SharePoint Online Management Shell](https://learn.microsoft.com/powershell/sharepoint/sharepoint-online/introduction-sharepoint-online-management-shell?view=sharepoint-ps).
 
diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Upgrade-SPOSite.md b/sharepoint/sharepoint-ps/sharepoint-online/Upgrade-SPOSite.md
@@ -32,7 +32,7 @@ When upgrade is initiated, it can either be a build-to-build or version-to-versi
 The default is build-to-build upgrade.
 When in version-to-version upgrade, site collection health checks are first run in repair mode to ensure that the site collection can be upgraded successfully.
 
-You must be a SharePoint Online administrator or Global Administrator and be a site collection administrator to run the cmdlet.
+You must be at least a SharePoint Online administrator and be a site collection administrator to run the cmdlet.
 
 For permissions and the most current information about Windows PowerShell for SharePoint Online, see the online documentation at [Intro to SharePoint Online Management Shell](https://learn.microsoft.com/powershell/sharepoint/sharepoint-online/introduction-sharepoint-online-management-shell?view=sharepoint-ps).
 
