SharePoint provides powerful collaboration features to users including lists and libraries, and while transparency is crucial, there are instances where hiding a list or library becomes essential for optimizing user experiences and/or maintaining data integrity. Example: Power Apps often relies on SharePoint lists as data sources. However, not all lists are meant for end users to view directly. By hiding lists or libraries from SharePoint UI, you can prevent end users from editing the data directly from SharePoint lists.
In this blog post, we’ll explore how to hide a SharePoint list or document library using PnP PowerShell & CLI for Microsoft 365 and view all hidden lists/libraries in SharePoint site using PnP PowerShell & CLI for Microsoft 365.
Hiding a SharePoint List or Library using PnP PowerShell
You can use below PnP PowerShell script to hide a SharePoint online list or document library from SharePoint UI (Site Contents page):
# SharePoint Online site URL $siteUrl = Read-Host -Prompt "Enter your SharePoint online site URL (e.g https://contoso.sharepoint.com/sites/work)"
# Display name of SharePoint online list or document library $listName = Read-Host -Prompt "Enter the display name of your SharePoint list or library (e.g My List)"
# Connect to SharePoint online site Connect-PnPOnline -url $siteUrl -Interactive
# Hide SharePoint online list from UI Set-PnPList -Identity $listName -Hidden $true
Hide a SharePoint List or Library using CLI for Microsoft 365
Use below CLI for Microsoft 365 script to hide a SharePoint list or document library from SharePoint UI:
# SharePoint Online site URL $siteUrl = Read-Host -Prompt "Enter your SharePoint online site URL (e.g https://contoso.sharepoint.com/sites/work)"
# Display name of SharePoint online list or document library $listName = Read-Host -Prompt "Enter the display name of your SharePoint list or library (e.g My List)"
# Get Credentials to connect $m365Status = m365 status if ($m365Status -match "Logged Out") { m365 login }
# Hide SharePoint online list or library from UI (Site Contents) m365 spo list set --webUrl $siteUrl --title $listName --hidden true
View hidden lists/libraries in SharePoint site using CLI for Microsoft 365
Use below CLI for Microsoft 365 script to view all hidden lists and document libraries in the given SharePoint online site:
# SharePoint Online site URL $siteUrl = Read-Host -Prompt "Enter your SharePoint online site URL (e.g https://contoso.sharepoint.com/sites/work)"
# Get Credentials to connect $m365Status = m365 status if ($m365Status -match "Logged Out") { m365 login }
# Hide SharePoint online list or library from UI (Site Contents) m365 spo list list --webUrl $siteUrl --properties "Id,Title,Url" --filter "Hidden eq true" | ConvertFrom-Json
The internal name of a SharePoint column is a unique name that is automatically generated by SharePoint when a column is created. It is used by SharePoint internally to reference and retrieve the value of a particular column associated with an item or document. The internal name is generated based on the display name you provide but all special characters and spaces will be replaced with Unicode’s by SharePoint. Internal name is generated only once while creating a new column and it cannot be changed even if you change the display name of SharePoint column.
The internal name is not visible to users in the SharePoint user interface by default, but it is commonly used in various scenarios, such as in SharePoint REST APIs, Power Automate flow expressions, Power Apps formulas, PowerShell, etc. to interact with column data programmatically.
Where are Internal names of SharePoint columns used?
Custom Scripts: When creating custom scripts, such as JavaScript or PowerShell, the internal names of columns are required to reference and manipulate the values of the columns while interacting with SharePoint data.
Workflows: In SharePoint Designer workflows or Microsoft Power Automate (formerly known as Microsoft Flow), the internal names of columns are used to reference the values of the columns as inputs or outputs in the workflow actions and in expressions.
Custom Solutions: When building custom solutions, such as SharePoint apps, SharePoint framework (SPFx) web parts, or custom code, the internal names of columns are required to interact with the columns programmatically.
Power Apps: Few of the Power Apps functions like ShowColumns, SortByColumns, etc. requires using internal names of SharePoint columns in formula.
JSON Formatting: Internal name of SharePoint column is required in JSON formatting to reference the column value with [$InternalNameOfColumn] syntax.
How to find the Internal name of a SharePoint column?
Using Modern experience list view
You can use sorting or filtering options from SharePoint online modern experience list view to find the internal name of a SharePoint column. Sort by and Filter by options are supported by most of the column types in SharePoint like Single line of text, Choice, Number, Date and Time, Yes/No (Boolean), Person or Group (single selection), etc.
For this afticle, we will use sorting based on SharePoint choice column as an example:
1. Go to the SharePoint online list for which you want to check the internal name of a column.
2. Click on column name/header from the list view and select either Ascending (A to Z) or Descending (Z to A) option from the popup menu:
Find internal name of SharePoint column by sorting choice column
3. SharePoint will sort the list view based on selection and the browser URL will be changed like:
Where column name (ChoiceColumn) after sortField= is the internal name of your SharePoint choice column.
4. Similarly, when you use Filter by option in SharePoint modern experience to filter the list view based on Date and Time column (named as Start Date), SharePoint changes browser URL like:
Where column name (Start_x0020_Date) after FilterField1= is the internal name of your SharePoint date and time column. Notice _x0020_ in internal column name which is an Unicode encoding of the space character in the display name of date and time column (Start Date).
Using Classic experience List settings page
Few of the SharePoint column types like Multiple lines of text, Hyperlink or Picture, Image, etc. does not support sorting or filtering from SharePoint modern experience list views. So, you have to use the classic experience list settings page to find the internal name for such SharePoint columns.
Follow below steps to find the internal name of multiple lines of text column using SharePoint classic experience list settings page:
1. Go to the SharePoint online list for which you want to check the internal name of a column.
2. Click on Settings (gear) icon from the top right corner and select List settings:
Open SharePoint online list settings page
3. From list settings page, scroll down to the Columns section and click on the column name for which you want to find the internal name:
Open SharePoint online Column settings page
4. SharePoint will open column settings page for the respective column with browser URL like:
SharePoint online column settings page showing internal name of column
Where column name (MultilineTextCol) after Field= is the internal name of your SharePoint online multiple lines of text column.
Note: You can use this classic experience method to find out the internal name of SharePoint columns for all column types.
Using SharePoint REST API
You can use SharePoint REST API endpoint like below to get the internal name of SharePoint column based on it’s display name. Open URL in below format directly from browser tab:
https://contoso.sharepoint.com/sites/SPConnect/_api/web/lists/getbytitle('InternalNames')/fields?$select=Title,InternalName&$filter=Title eq 'Multiline Text Column'
Find internal name of SharePoint column using SharePoint REST API
Using PnP PowerShell
You can use below PnP PowerShell script to find the internal name of SharePoint online list column using PnP PowerShell:
# SharePoint online site URL
$siteUrl = "https://contoso.sharepoint.com/sites/wlive"
# Display name of SharePoint list
$listName = "InternalNames"
# Display name of SharePoint list column
$columnName = "Multiline Text Column"
# Connect to SharePoint online site
Connect-PnPOnline -Url $siteUrl -Interactive
# Get internal name of SharePoint list column
Get-PnPField -Identity $columnName -List $listName | Select Title,InternalName
Find internal name of SharePoint column using PnP PowerShell
Using CLI for Microsoft 365
You can use below CLI for Microsoft 365 script to find the internal name of SharePoint online list column using CLI for Microsoft 365:
# SharePoint online site URL
$siteUrl = "https://contoso.sharepoint.com/sites/wlive"
# Display name of SharePoint list
$listName = "InternalNames"
# Display name of SharePoint list column
$columnName = "Multiline Text Column"
# Get Credentials to connect
$m365Status = m365 status
if ($m365Status -match "Logged Out") {
m365 login
}
# Get internal name of SharePoint list column
m365 spo field get --webUrl $siteUrl --listTitle $listName --title $columnName --output text
Find internal name of SharePoint column using CLI for Microsoft 365
Best practices for naming SharePoint columns
When creating columns in SharePoint, it’s important to follow best practices for column naming to avoid using special characters or Unicode characters in internal names. Here are some recommended best practices:
Use only alphanumeric characters: Stick to using letters (A-Z, a-z) and numbers (0-9) in column names. Avoid using special characters such as @, #, $, %, _, etc. Avoid column names beginning with numbers.
Avoid spaces: Use PascalCase to separate words in column names instead of spaces. For example, use ColumnName instead of Column Name. This can help prevent issues with URLs, Unicode encoding, and referencing column names in scripts or code.
Avoid reserved words: SharePoint has reserved words that are used for system functionality, and using them in column names may cause conflicts. Examples of reserved words include “ID”, “Modified”, “Created”, “Title”, etc. Avoid using these reserved words as column names.
Keep it concise and meaningful: Use descriptive and meaningful names for columns that clearly indicate their purpose. Avoid using vague or generic names that may be confusing or ambiguous to users. Use column description to provide more information about the columns.
Be consistent: Establish a consistent naming convention for columns across your SharePoint site or site collection to ensure uniformity and ease of management. This can also help with documentation, training, and maintenance of your SharePoint environment.
I hope you liked this article. Give your valuable feedback & suggestions in the comments section below and share this article with others.
SharePoint Online offers powerful web parts and features that enhance the visual appeal of your sites, including the ability to search for external images on the web while using web parts like Image, Hero, Image Gallery, Quick links, etc. While this feature can be valuable in various contexts, there are scenarios where organizations prefer to disable or hide the option to search for external images especially when they have created organization assets libraries in the SharePoint tenant.
In this blog post, we’ll explore how to hide/disable the “Web search” feature in SharePoint using SharePoint Online PowerShell, PnP PowerShell and CLI for Microsoft 365.
Using SharePoint Online PowerShell
Use below SharePoint Online PowerShell script to disable or enable external image “Web Search” feature in SharePoint Online tenant:
# SharePoint online admin center URL $adminCenterUrl = Read-Host -Prompt "Enter your SharePoint admin center site URL (e.g https://contoso-admin.sharepoint.com/)"
# Connect to SharePoint online admin center Connect-SPOService -Url $adminCenterUrl
You can use below PnP PowerShell script to hide/disable external image “Web Search” feature in SharePoint Online:
# SharePoint online admin center URL $adminCenterUrl = Read-Host -Prompt "Enter your SharePoint admin center site URL (e.g https://contoso-admin.sharepoint.com/)"
# Connect to SharePoint online admin center Connect-PnPOnline -Url $adminCenterUrl -Interactive
Disabling or hiding the web search for external images in SharePoint Online is a strategic choice for organizations that prioritize content security, brand consistency and compliance. By following the methods outlined in this blog post, you can tailor your SharePoint environment to align with your organization’s policies and enhance the overall governance of your digital assets.
In this blog post, we will explore how to remove or unregister a SharePoint online document library from organization assets libraries using PnP PowerShell and CLI for Microsoft 365.
Using PnP PowerShell
You can use below PnP PowerShell script to remove a SharePoint document library that was designated as a central location for organization assets across the tenant:
# URL of SharePoint online document library $libraryUrl = "https://contoso.sharepoint.com/sites/OrgAssets/CompanyLogos"
# SharePoint online admin center URL $adminCenterUrl = Read-Host -Prompt "Enter your SharePoint admin center site URL (e.g https://contoso-admin.sharepoint.com/)"
# Connect to SharePoint online admin center Connect-PnPOnline -Url $adminCenterUrl -Interactive
Note: It might take up to 24 hours to remove an organization assets library from “Your organization” tab in the file/image picker after you unregister it from the SharePoint tenant organization asset libraries.
In my previous blog post – Create an Organization Assets Library in SharePoint Online, I explained what is an Organization Assets Library in SharePoint, different types of organization assets libraries and provided a step-by-step guide on how to create organization assets libraries in SharePoint Online using SharePoint Online PowerShell.
In this blog post, we will explore how to register a SharePoint online document library as an organization assets library using PnP PowerShell and CLI for Microsoft 365. Before using below PowerShell scrips, follow this blog post until step #3 to create a SharePoint online communication site, granting proper permissions on the site and creating document libraries as per your requirements.
Using PnP PowerShell
You can use below PnP PowerShell script to register a SharePoint online document library as an organization assets library:
# URL of SharePoint online document library $libraryUrl = "https://contoso.sharepoint.com/sites/OrgAssets/CompanyLogos"
# Type of Organization assets library - ImageDocumentLibrary or OfficeTemplateLibrary $orgAssetType = "ImageDocumentLibrary"
# SharePoint online admin center URL $adminCenterUrl = Read-Host -Prompt "Enter your SharePoint admin center site URL (e.g https://contoso-admin.sharepoint.com/)"
# Connect to SharePoint online admin center Connect-PnPOnline -Url $adminCenterUrl -Interactive
# Register a document library as an organization assets library Add-PnPOrgAssetsLibrary -LibraryUrl $libraryUrl -OrgAssetType $orgAssetType
SharePoint Online and Microsoft Lists offers a multitude of features to enhance collaboration and streamline data management. One such feature is the Quick Property Editing (Edit in Grid view), which allows users to bulk edit metadata for multiple list items directly from the list view. While this feature can improve efficiency, there are scenarios where disabling it becomes necessary. In this blog post, we’ll explore various methods to achieve this in SharePoint Online.
From SharePoint UI
Follow below steps to disable quick edit (Edit in grid view) from SharePoint list UI:
1. Go to your SharePoint Online list.
2. Click on Settings (gear icon) from the top right corner and select List settings.
3. Click on Advanced settings link from List settings page.
4. From Advanced settings page, scroll down and set Quick property editing (Allow items in this list to be edited using Quick Edit and the Details Pane?) to No.
5. Click OK button at the bottom of advanced list settings page.
Using PnP PowerShell
You can use below PnP PowerShell script to disable Quick property editing (Grid view) from SharePoint Online list or document library:
# Display name of SharePoint online list or document library $listName = "My SharePoint List"
# SharePoint online site URL $siteUrl = Read-Host -Prompt "Enter your SharePoint site URL (e.g https://contoso.sharepoint.com/sites/pnppowershell)"
# Connect to SharePoint online site Connect-PnPOnline -Url $siteUrl -Interactive
# Disable Quick property editing (Grid view) from SharePoint list Set-PnPList -Identity $listName -DisableGridEditing $true
In my previous blog post Creating Colored Folders in SharePoint Online and OneDrive, we saw how to create colored folders in SharePoint online document libraries and OneDrive for Business using user interface (UI) from browser. In this blog post, we’ll explore how to create colorful folders in SharePoint Online using CLI for Microsoft 365, a powerful command-line tool that extends SharePoint’s capabilities.
This new feature of coloring SharePoint & OneDrive folders allows users to assign a color label to folders, providing a visual cue for organization and categorization. However, it’s essential to understand how this works internally and what values are used for coloring folders in SharePoint Online and OneDrive for Business.
Thanks to Tetsuya Kawahara and his PnP PowerShell script sample at Create Colored Folder which explains SharePoint uses the column with internal name as _ColorHex to store the color setting information of folders. The _ColorHex field is a hidden field within SharePoint libraries, and it is not visible by default in standard views. This field stores the color as a numeric value corresponding to each color.
SharePoint supports a predefined set of 16 numerical color values that can be used to color folders. The following table shows the numerical values corresponding to each color:
Color
_ColorHex value
Yellow
Empty or 0
Dark red
1
Dark orange
2
Dark green
3
Dark teal
4
Dark blue
5
Dark purple
6
Dark pink
7
Grey
8
Light red
9
Light orange
10
Light green
11
Light teal
12
Light blue
13
Light purple
14
Light pink
15
We will see how to use these _ColorHex column values to create a new folder in SharePoint online document library using CLI for Microsoft 365 below:
Step 1: Install the CLI for Microsoft 365
Before we can start working with the CLI for Microsoft 365, we need to install it. You can install the CLI for Microsoft 365 by using below NPM commands or by following the instructions on the official documentation page: CLI for Microsoft 365 – Installation.
npm install -g @pnp/cli-microsoft365
You have to use below command if you want to install beta version of CLI for Microsoft 365:
npm install -g @pnp/cli-microsoft365@next
Step 2: Create colored folder using CLI for Microsoft 365
After installation of CLI for Microsoft 365, you can use below CLI for Microsoft 365 script to create a new colored folder in SharePoint online document library using CLI for Microsoft 365:
# Set Variables
$siteUrl = "https://contoso.sharepoint.com/sites/work"
$relativeUrlOfParentFolder = "/ColoredFolders"
$documentLibraryDisplayName = "Colored Folders"
$folderName = "Confidential"
$folderColor = 1
try {
# Get Credentials to connect to SharePoint Online site
$m365Status = m365 status
if ($m365Status -match "Logged Out") {
m365 login
}
# Create the folder
$newFolder = m365 spo folder add --webUrl $siteUrl --parentFolderUrl $relativeUrlOfParentFolder --name $folderName | ConvertFrom-Json
# Get the created folder item
$newFolderItem = m365 spo listitem get --webUrl $siteUrl --listTitle $documentLibraryDisplayName --uniqueId $newFolder.UniqueId | ConvertFrom-Json
# Change the value of the _ColorHex column of the created folder to change the color
m365 spo listitem set --webUrl $siteUrl --listTitle $documentLibraryDisplayName --id $newFolderItem.Id --_ColorHex $folderColor
Write-Host "Folder created and color changed successfully." -ForegroundColor Green
Write-Host "Folder URL: $siteUrl/$relativeUrlOfParentFolder/$folderName" -ForegroundColor Green
}
catch {
Write-Host "An error occurred: $_" -ForegroundColor Red
}
finally {
# Disconnect from SharePoint site
m365 logout
}
Once you run above script successfully and navigate to SharePoint document library, you will see that new colored folder is created inside the SharePoint document library as given below:
Colored folders created in SharePoint Online using CLI for Microsoft 365
Conclusion
Adding color to your folders in SharePoint Online document libraries using CLI for Microsoft 365 is a simple yet effective way to enhance the visual organization and management of your documents. This can improve user experience and help users quickly identify and access the content they need. Experiment with different colors and organizational schemes to find what works best for your team or organization.
You can use any one of the approaches given below for enabling or disabling the Social Bar (Like, No. of Comments, Views, Save for later) for individual SharePoint online sites.
Using SharePoint Online PowerShell
Use below SharePoint Online PowerShell script to enable or disable the social bar from site pages for specific SharePoint online modern experience site:
# SharePoint online admin center URL
$adminCenterUrl = Read-Host -Prompt "Enter your SharePoint online admin center URL (e.g https://contoso-admin.sharepoint.com/)"
# Connect to SharePoint online admin center
Connect-SPOService -Url $adminCenterUrl
# SharePoint online site URL
$siteUrl = Read-Host -Prompt "Enter your SharePoint site URL (e.g https://contoso.sharepoint.com/sites/work)"
# Disable the social bar from SharePoint online site pages
Set-SPOSite -Identity $siteUrl -SocialBarOnSitePagesDisabled $true
# Enable the social bar on SharePoint online site pages
Set-SPOSite -Identity $siteUrl -SocialBarOnSitePagesDisabled $false
# Disconnect SharePoint online connection
Disconnect-SPOService
Using PnP PowerShell
You can use below PnP PowerShell script to show or hide the social bar from SharePoint online modern experience site pages for individual SharePoint site:
# SharePoint online site URL
$siteUrl = Read-Host -Prompt "Enter your SharePoint site URL (e.g https://contoso.sharepoint.com/sites/work)"
# Connect to SharePoint online site
Connect-PnPOnline -Url $siteUrl -Interactive
# Hide the social bar from SharePoint online modern site pages
Set-PnPSite -SocialBarOnSitePagesDisabled $true
# Show the social bar on SharePoint online modern site pages
Set-PnPSite -SocialBarOnSitePagesDisabled $false
# Disconnect SharePoint online connection
Disconnect-PnPOnline
Using CLI for Microsoft 365
Use below CLI for Microsoft script to show or hide the social bar from SharePoint online modern experience site pages for individual SharePoint site:
# SharePoint online site URL
$siteUrl = Read-Host -Prompt "Enter your SharePoint site URL (e.g https://contoso.sharepoint.com/sites/work)"
# Connect to SharePoint online tenant
$m365Status = m365 status
if ($m365Status -match "Logged Out") {
m365 login
}
# Hide the social bar from SharePoint online modern site pages
m365 spo site set --url $siteUrl --socialBarOnSitePagesDisabled true
# Show the social bar on SharePoint online modern site pages
m365 spo site set --url $siteUrl --socialBarOnSitePagesDisabled false
# Disconnect SharePoint online connection
m365 logout
Conclusion
By using the PowerShell scripts given in this blog post, you can enable or disable social bar features from SharePoint online modern site pages for specific SharePoint online sites.
SharePoint Online provides various social features in modern experience SharePoint sites. One of the features available for SharePoint site pages is the social bar (Like, No. of Comments, Views, Save for later), which is situated at the bottom of site pages. Social bar allows users to engage with page content by liking and saving pages for later reference. Social bar also shows the number of page views and comments on modern site pages.
However, organizations may have specific requirements that necessitate enabling or disabling the social bar on SharePoint site pages. Unfortunately, there are no settings available for enabling/disabling social bar using SharePoint user interface. In this blog post, we will explore how to achieve this at SharePoint tenant level using SharePoint Online PowerShell, PnP PowerShell and CLI for Microsoft 365 scripts.
Using SharePoint Online PowerShell
Use below SharePoint Online PowerShell script to enable or disable the social bar from site pages for all SharePoint sites in the tenant:
# SharePoint online admin center URL
$adminCenterUrl = "https://contoso-admin.sharepoint.com/"
# Connect to SharePoint online admin center
Connect-SPOService -Url $adminCenterUrl
# Disable the social bar from SharePoint online site pages
Set-SPOTenant -SocialBarOnSitePagesDisabled $true
# Enable the social bar on SharePoint online site pages
Set-SPOTenant -SocialBarOnSitePagesDisabled $false
Using PnP PowerShell
You can use below PnP PowerShell script to show or hide the social bar from SharePoint online modern experience site pages:
# SharePoint online admin center URL
$adminCenterUrl = "https://contoso-admin.sharepoint.com/"
# Connect to SharePoint online admin center
Connect-PnPOnline -Url $adminCenterUrl -Interactive
# Show the social bar on SharePoint online modern site pages
Set-PnPTenant -SocialBarOnSitePagesDisabled $false
# Hide the social bar from SharePoint online modern site pages
Set-PnPTenant -SocialBarOnSitePagesDisabled $true
Using CLI for Microsoft 365
Use below CLI for Microsoft 365 script to enable or disable the Social Bar (like, No. of comments, views, Save for later) in SharePoint online at tenant level:
# Get Credentials to connect
$m365Status = m365 status
if ($m365Status -match "Logged Out") {
m365 login
}
# Disable the social bar from SharePoint online site pages
m365 spo tenant settings set --SocialBarOnSitePagesDisabled true
# Enable the social bar on SharePoint online site pages
m365 spo tenant settings set --SocialBarOnSitePagesDisabled false
Conclusion
Enabling or disabling the social bar on site pages in SharePoint Online can be achieved using SharePoint Online PowerShell, PnP PowerShell or CLI for Microsoft 365 scripts. By following the steps outlined in this blog post, you can customize the user experience and align it with your organization’s specific requirements. Whether you want to encourage user engagement or disable social features for certain scenarios, these PowerShell scripts provide the flexibility to control the social bar’s presence on SharePoint online modern site pages.
SharePoint Online is a powerful collaboration and content management platform that allows organizations to create and manage sites for various purposes. One of the key features that enhances site design and improves user experience is the use of Page Templates. In this blog post, we will delve into what are page templates in SharePoint online and how to set a default page template for a SharePoint site.
What are Page Templates in SharePoint?
Page templates in SharePoint Online are pre-designed layouts or structures that provide a consistent and standardized format for creating site pages within a site. They serve as a starting point for designing and organizing content on SharePoint pages, ensuring a cohesive look and feel across the site.
Page templates can include a variety of elements such as placeholders for text, images, web parts, page sections, and more. By using page templates, users can quickly create new pages with a predefined structure and layout, saving time and effort while maintaining visual consistency.
Setting a Default Page Template for a SharePoint Site
When users try to create new site pages from SharePoint site home page, the default selected template in the Page Templates pane is Blank. If users don’t select a different template, the blank template will be used for their new page.
If you prefer to have another custom page template be the default selection for your SharePoint site while creating new site pages, follow one of the methods given below:
Using SharePoint User Interface
Follow below steps to set a default page template for your SharePoint online site from SharePoint UI:
1. Go to home page of your SharePoint online site.
2. Click on New from page command bar and select Page:
Open Page templates pane from SharePoint online site home page
3. Click on vertical ellipses at the bottom right side of the template you want, and then select Set default selection:
Set default selection of page template for SharePoint site
4. Click OK from Changing default selection confirmation popup.
Note: When you change the default selection in the page templates pane, it will be changed for all users in the SharePoint site.
Using PnP PowerShell
You can use below PnP PowerShell script to set a page template as default page template for SharePoint online site:
# SharePoint online site URL
$siteUrl = Read-Host -Prompt "Enter your SharePoint site URL (e.g https://contoso.sharepoint.com/sites/work)"
# Connect to SharePoint online site
Connect-PnPOnline -Url $siteUrl -Interactive
# Get page template details and Unique ID
$page = Get-PnPFile -Url "/sites/work/SitePages/Templates/PlainHeaderNoComments.aspx" -AsListItem
# Set a page template as default page template for SharePoint online site
Set-PnPPropertyBagValue -Key DefaultNewPageTemplateId -Value $page["UniqueId"]
# Disconnect SharePoint online connection
Disconnect-PnPOnline
You may get error like below while executing above PnP PowerShell script if custom scripts are not enabled for your SharePoint site:
Set-PnPPropertyBagValue: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)) Site might have NoScript enabled, this prevents setting some property bag values.
Use below CLI for Microsoft 365 script to set a page template as default page template for SharePoint online site:
# Get Credentials to connect
$m365Status = m365 status
if ($m365Status -match "Logged Out") {
m365 login
}
# SharePoint online site URL
$siteUrl = Read-Host -Prompt "Enter your SharePoint site URL (e.g https://contoso.sharepoint.com/sites/work)"
# Get page template details and Unique ID
$page = m365 spo file get --webUrl $siteUrl --url '/sites/work/SitePages/Templates/PlainHeaderNoComments.aspx' | ConvertFrom-Json
# Set a page template as default page template for SharePoint online site
m365 spo propertybag set --webUrl $siteUrl --key DefaultNewPageTemplateId --value $page.UniqueId
If custom scripts are not enabled for your SharePoint site, above CLI for Microsoft 365 script will throw error like:
Error: Site has NoScript enabled, and setting property bag values is not supported
Page templates in SharePoint online provide a valuable tool for enhancing site design and improving user experience. By setting a default page template, organizations can establish a consistent and standardized format for creating web pages within their SharePoint sites. This not only saves time but also ensures a cohesive and professional look across the site. By leveraging page templates, organizations can effectively showcase their content while maintaining their branding and style guidelines.
SharePoint online is a powerful platform that allows users to create and manage websites and content, collaborate with others, and more. However, SharePoint out-of-the-box features may not always meet the specific needs of your organization.
Fortunately, SharePoint online allows the use of custom scripts, which can be used to enhance the platform’s functionality and customize it to your specific needs.
When you allow the use of custom scripts in SharePoint online sites, users gain access to a wide range of features and functionalities. Here are some of the key capabilities that become available:
Web Parts: Users can use classic experience web parts like Script Editor, Content Editor (and lot more) using which they can create custom web parts using client-side scripting languages like JavaScript or TypeScript.
Use of Save Site as Template, Save document library as template, etc. features in SharePoint.
Use of Solution Gallery, Theme Gallery, Sandbox solutions, HTML Field Security, etc. settings in SharePoint sites.
Uploading files types that are blocked by default like .asmx.ascx.aspx.htc.jar.master.swf.xap.xsf
Let’s see how you can allow or prevent use of custom scripts in SharePoint Online sites using different PowerShell tools:
Using SharePoint Online PowerShell
Use below SharePoint Online PowerShell script to check if custom scripts are enabled or disabled for a SharePoint online site and then to allow use of custom scripts for specified SharePoint online site:
# SharePoint online admin center URL
$adminCenterUrl = "https://contoso-admin.sharepoint.com/"
# SharePoint online site URL
$siteUrl = "https://contoso.sharepoint.com/sites/SPConnect"
# Connect to SharePoint online admin center
Connect-SPOService -Url $adminCenterUrl
# Allow custom scripts on SharePoint online site
Set-SPOSite $siteUrl -DenyAddAndCustomizePages 0
# Verify that custom scripts are enabled on SharePoint online site
Get-SPOSite $siteUrl | select DenyAddAndCustomizePages
Using PnP PowerShell
You can use below PnP PowerShell script to allow or prevent use of custom scripts in SharePoint online site:
# SharePoint online site URL
$siteUrl = "https://contoso.sharepoint.com/sites/SPConnect"
# Connect to SharePoint online site
Connect-PnPOnline -Url $siteUrl -Interactive
# Allow custom scripts on SharePoint online site
Set-PnPSite -NoScriptSite $false
# Prevent custom scripts on SharePoint online site
Set-PnPSite -NoScriptSite $true
Using CLI For Microsoft 365
Use below CLI for Microsoft 365 script to allow use of custom scripts in SharePoint online site collection:
# SharePoint online site URL
$siteUrl = "https://contoso.sharepoint.com/sites/SPConnect"
# Connect to SharePoint online tenant
$m365Status = m365 status
if ($m365Status -match "Logged Out") {
m365 login
}
# Allow custom scripts on SharePoint online site collection
m365 spo site set --url $siteUrl --noScriptSite $false
Conclusion
Enabling custom script support for SharePoint online sites can enhance the platform’s functionality and enable users to customize site to their specific needs. However, it’s important to carefully consider the potential security risks before enabling this feature, check: security considerations of allowing custom scripts in SharePoint.
In this blog, I will explain how to create a new list item with image column and update existing list item to update the image column using CLI for Microsoft 365.
Create new list item with Image column
You can use below CLI for Microsoft 365 script to create a new item in SharePoint online list with Image column:
# SharePoint online site URL
$siteUrl = Read-Host -Prompt "Enter your site URL (e.g https://<tenant>.sharepoint.com/sites/contoso)"
# Server Relative URL of image file from same SharePoint site
$serverRelativeUrl = Read-Host -Prompt "Enter Server Relative URL of image file (e.g /sites/contoso/SiteAssets/Lists/dbc6f551-252b-462f-8002-c8f88d0d12d5/CLI-For-Microsoft-365-Blue.png)"
# Get Credentials to connect
$m365Status = m365 status
if ($m365Status -match "Logged Out") {
m365 login
}
# Get UniqueId of file you're referencing (without this part your image won't appear in Power Apps (browser or mobile app) or Microsoft Lists (iOS app))
$imageFileUniqueId = (m365 spo file get --webUrl $siteUrl --url $serverRelativeUrl | ConvertFrom-Json).UniqueId
# Create new list item with image column
m365 spo listitem add --listTitle "Logo Universe" --webUrl $siteUrl --Title "CLI for Microsoft 365" --Image "{'type':'thumbnail','fileName':'CLI-For-Microsoft-365-Blue.png','fieldName':'Image','serverUrl':'https://contoso.sharepoint.com','serverRelativeUrl':'$($serverRelativeUrl)', 'id':'$($imageFileUniqueId)'}"
# Disconnect SharePoint online connection
m365 logout
Create new list item with Image column
Update SharePoint list item with Image column
You can use below CLI for Microsoft 365 script to update existing SharePoint list item with Image column:
# SharePoint online site URL
$siteUrl = Read-Host -Prompt "Enter your site URL (e.g https://<tenant>.sharepoint.com/sites/contoso)"
# Server Relative URL of image file from same SharePoint site
$serverRelativeUrl = Read-Host -Prompt "Enter Server Relative URL of image file (e.g /sites/contoso/SiteAssets/Lists/dbc6f551-252b-462f-8002-c8f88d0d12d5/CLI-For-Microsoft-365-Blue.png)"
# Get Credentials to connect
$m365Status = m365 status
if ($m365Status -match "Logged Out") {
m365 login
}
# Get UniqueId of file you're referencing (without this part your image won't appear in Power Apps (browser or mobile app) or Microsoft Lists (iOS app))
$imageFileUniqueId = (m365 spo file get --webUrl $siteUrl --url $serverRelativeUrl | ConvertFrom-Json).UniqueId
# Update list item with image column
m365 spo listitem set --listTitle "Logo Universe" --id 15 --webUrl $siteUrl --Image "{'type':'thumbnail','fileName':'CLI-For-Microsoft-365-Blue.png','fieldName':'Image','serverUrl':'https://contoso.sharepoint.com','serverRelativeUrl':'$($serverRelativeUrl)', 'id':'$($imageFileUniqueId)'}"
# Disconnect SharePoint online connection
m365 logout
In SharePoint online, you can use Site templates (previously known as “Site designs”) and Site scripts to provide reusable site columns, content types, lists, themes, site navigation layouts, or custom actions so that your users can quickly build new SharePoint sites with the features they need. SharePoint custom site scripts can help you to add custom branding, theming, or automation like setting a site logo, activating a site feature, etc. to your SharePoint online site.
However, over time, these custom site scripts can become outdated or unnecessary and ends up just hanging around in your SharePoint tenant for a long time even though you no longer need them. In this blog, we will discuss how to delete the custom SharePoint site scripts using PowerShell “scripts” (pun intended).
Using SharePoint Online PowerShell
You can run below SharePoint online PowerShell script from SharePoint Online Management Shell to delete the custom site scripts in your tenant:
# SharePoint online admin site URL
$siteUrl = "https://contoso-admin.sharepoint.com/"
# Connect to SharePoint online admin center
Connect-SPOService -Url $siteUrl
# Get all site scripts from the current tenant
$siteScripts = Get-SPOSiteScript
# List of custom site scripts to exclude from deletion
$keepThese = "Base Site Settings", "English Region", "Standard Site Columns", "Standard Libraries"
$siteScripts = $siteScripts | Where-Object { -not ($keepThese -contains $_.Title)}
if ($siteScripts.Count -eq 0) { break }
$siteScripts | Format-Table Title, SiteScriptIds, Description
Read-Host -Prompt "Press Enter to start deleting (CTRL + C to exit)"
$progress = 0
$total = $siteScripts.Count
foreach ($siteScript in $siteScripts)
{
$progress++
Write-Host $progress / $total":" $siteScript.Title
# Delete custom site script
Remove-SPOSiteScript -Identity $siteScript.Id
}
# Disconnect SharePoint online connection
Disconnect-SPOService
Using PnP PowerShell
Use below PnP PowerShell script to delete the custom site scripts from SharePoint online tenant:
# SharePoint online admin site URL
$siteUrl = "https://contoso-admin.sharepoint.com/"
# Connect to SharePoint online admin center
Connect-PnPOnline -Url $siteUrl -Interactive
# Get all site scripts from the current tenant
$siteScripts = Get-PnPSiteScript
# List of custom site scripts to exclude from deletion
$keepThese = "Base Site Settings", "English Region", "Standard Site Columns", "Standard Libraries"
$siteScripts = $siteScripts | Where-Object { -not ($keepThese -contains $_.Title)}
if ($siteScripts.Count -eq 0) { break }
$siteScripts | Format-Table Title, SiteScriptIds, Description
Read-Host -Prompt "Press Enter to start deleting (CTRL + C to exit)"
$progress = 0
$total = $siteScripts.Count
foreach ($siteScript in $siteScripts)
{
$progress++
Write-Host $progress / $total":" $siteScript.Title
# Delete custom site script
Remove-PnPSiteScript -Identity $siteScript.Id
}
# Disconnect SharePoint online connection
Disconnect-PnPOnline
Using CLI for Microsoft 365
Use below CLI for Microsoft 365 script to remove custom SharePoint site scripts from your tenant:
# Get credentials to connect to SharePoint online tenant
$m365Status = m365 status
if ($m365Status -match "Logged Out") {
m365 login
}
# Get all site scripts from the current tenant
$siteScripts = m365 spo sitescript list | ConvertFrom-Json
# List of custom site scripts to exclude from deletion
$keepThese = "Base Site Settings", "English Region", "Standard Site Columns", "Standard Libraries"
$siteScripts = $siteScripts | Where-Object { -not ($keepThese -contains $_.Title)}
if ($siteScripts.Count -eq 0) { break }
$siteScripts | Format-Table Title, SiteScriptIds, Description
Read-Host -Prompt "Press Enter to start deleting (CTRL + C to exit)"
$progress = 0
$total = $siteScripts.Count
foreach ($siteScript in $siteScripts)
{
$progress++
Write-Host $progress / $total":" $siteScript.Title
# Delete custom site script
m365 spo sitescript remove --id $siteScript.Id
}
# Disconnect SharePoint online connection
m365 logout
SharePoint Online lists are a great way to organize and manage data within your organization. They provide a flexible and customizable platform for teams to collaborate and share information. One of the features available in SharePoint Online lists / Microsoft Lists is the ability to add comments to list items. This can be a useful way to provide feedback, ask questions, or share information related to specific items within the list.
However, there may be situations where you want to disable comments for a particular list. This could be because you want to limit the amount of noise or clutter in the comments section, or because you want to encourage users to provide feedback in a different way.
In this blog post, we will walk through the steps required to enable or disable comments for a SharePoint Online list using the CLI for Microsoft 365.
Step 1: Install the CLI for Microsoft 365
Before we can start working with the CLI for Microsoft 365, we need to install it. You can install the CLI for Microsoft 365 by using below NPM commands or by following the instructions on the official documentation page: CLI for Microsoft 365 – Installation. You have to install CLI for M365 v6.7.0 (beta) or higher.
npm install -g @pnp/cli-microsoft365
You have to use below command if you want to install beta version of CLI for Microsoft 365:
npm install -g @pnp/cli-microsoft365@next
Step 2: Enable or Disable Comments for a SharePoint Online List
To enable or disable comments for a SharePoint Online list, we have to use the m365 spo list set command in the CLI for Microsoft 365. The syntax for this command is as follows:
m365 spo list set --webUrl <site url> --title <list title> --disableCommenting <true/false>
Let’s break down each of these parameters:
--webUrl: The URL of the SharePoint Online site where the list is located.
--title: The title of the list you want to enable or disable comments for.
--disableCommenting: Set this to true to disable comments, or false to enable comments.
Here’s a complete CLI for Microsoft 365 script which you can use to disable comments for a SharePoint Online/Microsoft Lists modern experience list:
# SharePoint online site URL
$siteUrl = "https://contoso.sharepoint.com/sites/SPConnect"
# Display name of SharePoint list
$listName = "Comments List"
# Get Credentials to connect to SharePoint site
$m365Status = m365 status
if ($m365Status -match "Logged Out") {
m365 login
}
# Disable SharePoint online list comments
m365 spo list set --webUrl $siteUrl --title $listName --disableCommenting true
You can modify this CLI for M365 script to enable SharePoint list comments by changing the --disableCommenting parameter to false.
Once you run above script successfully, navigate to List Settings > Advanced Settings and you will find that commenting is disabled for your SharePoint online list:
Disabled commenting on SharePoint Online list using CLI for Microsoft 365
The internal name of a SharePoint column is a unique name that is automatically generated by SharePoint when a column is created. It is used by SharePoint internally to reference and retrieve the value of a particular column associated with an item or document. The internal name is generated based on the display name you provide but all special characters and spaces will be replaced with Unicode’s by SharePoint. Internal name is generated only once while creating a new column and it cannot be changed even if you change the display name of SharePoint column.
The internal name is not visible to users in the SharePoint user interface by default, but it is commonly used in various scenarios, such as in SharePoint REST APIs, Power Automate flow expressions, Power Apps formulas, PowerShell, etc. to interact with column data programmatically.
Where are Internal names of SharePoint columns used?
Custom Scripts: When creating custom scripts, such as JavaScript or PowerShell, the internal names of columns are required to reference and manipulate the values of the columns while interacting with SharePoint data.
Workflows: In SharePoint Designer workflows or Microsoft Power Automate (formerly known as Microsoft Flow), the internal names of columns are used to reference the values of the columns as inputs or outputs in the workflow actions and in expressions.
Custom Solutions: When building custom solutions, such as SharePoint apps, SharePoint framework (SPFx) web parts, or custom code, the internal names of columns are required to interact with the columns programmatically.
Power Apps: Few of the Power Apps functions like ShowColumns, SortByColumns, etc. requires using internal names of SharePoint columns in formula.
JSON Formatting: Internal name of SharePoint column is required in JSON formatting to reference the column value with [$InternalNameOfColumn] syntax.
How to find the Internal name of a SharePoint column?
Using Modern experience list view
You can use sorting or filtering options from SharePoint online modern experience list view to find the internal name of a SharePoint column. Sort by and Filter by options are supported by most of the column types in SharePoint like Single line of text, Choice, Number, Date and Time, Yes/No (Boolean), Person or Group (single selection), etc.
For this afticle, we will use sorting based on SharePoint choice column as an example:
1. Go to the SharePoint online list for which you want to check the internal name of a column.
2. Click on column name/header from the list view and select either Ascending (A to Z) or Descending (Z to A) option from the popup menu:
Find internal name of SharePoint column by sorting choice column
3. SharePoint will sort the list view based on selection and the browser URL will be changed like:
Where column name (ChoiceColumn) after sortField= is the internal name of your SharePoint choice column.
4. Similarly, when you use Filter by option in SharePoint modern experience to filter the list view based on Date and Time column (named as Start Date), SharePoint changes browser URL like:
Where column name (Start_x0020_Date) after FilterField1= is the internal name of your SharePoint date and time column. Notice _x0020_ in internal column name which is an Unicode encoding of the space character in the display name of date and time column (Start Date).
Using Classic experience List settings page
Few of the SharePoint column types like Multiple lines of text, Hyperlink or Picture, Image, etc. does not support sorting or filtering from SharePoint modern experience list views. So, you have to use the classic experience list settings page to find the internal name for such SharePoint columns.
Follow below steps to find the internal name of multiple lines of text column using SharePoint classic experience list settings page:
1. Go to the SharePoint online list for which you want to check the internal name of a column.
2. Click on Settings (gear) icon from the top right corner and select List settings:
Open SharePoint online list settings page
3. From list settings page, scroll down to the Columns section and click on the column name for which you want to find the internal name:
Open SharePoint online Column settings page
4. SharePoint will open column settings page for the respective column with browser URL like:
SharePoint online column settings page showing internal name of column
Where column name (MultilineTextCol) after Field= is the internal name of your SharePoint online multiple lines of text column.
Note: You can use this classic experience method to find out the internal name of SharePoint columns for all column types.
Using SharePoint REST API
You can use SharePoint REST API endpoint like below to get the internal name of SharePoint column based on it’s display name. Open URL in below format directly from browser tab:
https://contoso.sharepoint.com/sites/SPConnect/_api/web/lists/getbytitle('InternalNames')/fields?$select=Title,InternalName&$filter=Title eq 'Multiline Text Column'
Find internal name of SharePoint column using SharePoint REST API
Using PnP PowerShell
You can use below PnP PowerShell script to find the internal name of SharePoint online list column using PnP PowerShell:
# SharePoint online site URL
$siteUrl = "https://contoso.sharepoint.com/sites/wlive"
# Display name of SharePoint list
$listName = "InternalNames"
# Display name of SharePoint list column
$columnName = "Multiline Text Column"
# Connect to SharePoint online site
Connect-PnPOnline -Url $siteUrl -Interactive
# Get internal name of SharePoint list column
Get-PnPField -Identity $columnName -List $listName | Select Title,InternalName
Find internal name of SharePoint column using PnP PowerShell
Using CLI for Microsoft 365
You can use below CLI for Microsoft 365 script to find the internal name of SharePoint online list column using CLI for Microsoft 365:
# SharePoint online site URL
$siteUrl = "https://contoso.sharepoint.com/sites/wlive"
# Display name of SharePoint list
$listName = "InternalNames"
# Display name of SharePoint list column
$columnName = "Multiline Text Column"
# Get Credentials to connect
$m365Status = m365 status
if ($m365Status -match "Logged Out") {
m365 login
}
# Get internal name of SharePoint list column
m365 spo field get --webUrl $siteUrl --listTitle $listName --title $columnName --output text
Find internal name of SharePoint column using CLI for Microsoft 365
Best practices for naming SharePoint columns
When creating columns in SharePoint, it’s important to follow best practices for column naming to avoid using special characters or Unicode characters in internal names. Here are some recommended best practices:
Use only alphanumeric characters: Stick to using letters (A-Z, a-z) and numbers (0-9) in column names. Avoid using special characters such as @, #, $, %, _, etc. Avoid column names beginning with numbers.
Avoid spaces: Use PascalCase to separate words in column names instead of spaces. For example, use ColumnName instead of Column Name. This can help prevent issues with URLs, Unicode encoding, and referencing column names in scripts or code.
Avoid reserved words: SharePoint has reserved words that are used for system functionality, and using them in column names may cause conflicts. Examples of reserved words include “ID”, “Modified”, “Created”, “Title”, etc. Avoid using these reserved words as column names.
Keep it concise and meaningful: Use descriptive and meaningful names for columns that clearly indicate their purpose. Avoid using vague or generic names that may be confusing or ambiguous to users. Use column description to provide more information about the columns.
Be consistent: Establish a consistent naming convention for columns across your SharePoint site or site collection to ensure uniformity and ease of management. This can also help with documentation, training, and maintenance of your SharePoint environment.
I hope you liked this article. Give your valuable feedback & suggestions in the comments section below and share this article with others.
SharePoint site home page provides a centralized location where users can access important information such as news, announcements, quick links and documents. This can help users stay informed and up-to-date on the latest company news and updates.
SharePoint site home page can be customized to include quick links to commonly used tools and applications, which can help users save time and increase productivity.
In this blog, we will look at how to use PnP PowerShell and CLI for Microsoft 365 to set a SharePoint modern page as the home page for SharePoint online site. You can use either of below scripts to make a newly created site page or an existing site page as the homepage for your SharePoint site.
Using PnP PowerShell
Once you have a modern site page ready in Site Pages library of your SharePoint site, you can use below PnP PowerShell script to make your site page as the homepage of your SharePoint site:
# SharePoint online site URL
$siteUrl = "https://contoso.sharepoint.com/sites/SPConnect"
# Name of your SharePoint site page
$sitePageName = "NewHome.aspx"
# Connect to SharePoint online site
Connect-PnPOnline -Url $siteUrl -Interactive
# Set SharePoint site home page using PnP PowerShell
Set-PnPHomePage -RootFolderRelativeUrl SitePages/$sitePageName
Using CLI for Microsoft 365
You can use below CLI for Microsoft script to set your site page as the homepage of your SharePoint online site:
# SharePoint online site URL
$siteUrl = "https://contoso.sharepoint.com/sites/SPConnect"
# Name of your SharePoint site page
$sitePageName = "NewHome.aspx"
#Get Credentials to connect
$m365Status = m365 status
if ($m365Status -match "Logged Out") {
m365 login
}
# Set SharePoint site home page using CLI for Microsoft 365
m365 spo web set --url $siteUrl --welcomePage "SitePages/$sitePageName"
Note
You have to install latest versions of PnP PowerShell and CLI for Microsoft 365 before running above scripts. Follow below documentations for installing PnP PowerShell and CLI for Microsoft 365:
Once you run either of above scripts successfully and navigate to SharePoint online site, you will see that new home page is set for your SharePoint online site:
Set SharePoint site home page using PnP PowerShell and CLI for Microsoft 365
SharePoint Online is a powerful platform for managing and sharing documents and other types of content within an organization. One of the key features of SharePoint Online is its ability to use JSON View formatting to customize the look and feel of lists and libraries.
However, applying JSON View formatting can be a time-consuming and repetitive task, especially if you need to apply the same formatting to multiple sites or lists. Fortunately, we have a command-line tool called CLI for Microsoft 365 that makes it easy to automate this process.
The first step is to install CLI for Microsoft 365. You can do this by following the instructions on the official documentation page: CLI for Microsoft 365 – Installation
Then you can use below CLI for Microsoft 365 script to apply JSON View formatting to your SharePoint online list:
# Display name of SharePoint list
$listName = "Ganesh Sanap Blogs"
# Name of SharePoint list view
$viewName = "All Items"
# JSON to apply to view formatting
$jsonViewFormatting = @'
{
"$schema": "https://developer.microsoft.com/json-schemas/sp/view-formatting.schema.json",
"additionalRowClass": "=if([$DueDate] <= @now, 'sp-field-severity--blocked', '')"
}
'@
# Get Credentials to connect
$m365Status = m365 status
if ($m365Status -match "Logged Out") {
m365 login
}
# Apply JSON view formatting
m365 spo list view set --webUrl $siteUrl --listTitle $listName --title $viewName --CustomFormatter $jsonViewFormatting
Once you run above script successfully and navigate to SharePoint list view, you will see that new JSON view formatting is applied to your SharePoint online list view using CLI for Microsoft 365:
SharePoint Online – Apply JSON View formatting using CLI for Microsoft 365
Conclusion
Using CLI for Microsoft 365, you can easily apply JSON View formatting to your SharePoint Online lists, saving time and reducing the risk of errors. By following the steps outlined in this blog post, you can quickly get started with using CLI for Microsoft 365 to apply JSON View formatting to your SharePoint Online lists.
SharePoint online home site is also required to use Microsoft Viva connections in Microsoft Teams desktop client.
So, if you are planning to customize the global navigation or use Microsoft Viva connections in Microsoft Teams, first you have to set up a home site for your SharePoint online tenant. Home site is a SharePoint site that you create and set as the top landing page for all users in your intranet. You can set only one SharePoint site as a home site which must be a communication site.
Steps to set a site as your home site
Create a communication site to set it as the home site or use existing communication site.
Customize the communication site by adding navigation, header, footer, site logo, news, events and other web parts as per your requirements and brand.
Use PowerShell commands to set a communication site as the home site.
Use PowerShell to set a communication site as the home site
After you create and customize the communication site that you want to use as your home site, you need to run a PowerShell commands to set it as your home site. To run this commands, you must be a global admin or SharePoint admin in your Microsoft 365 tenant.
You can use CLI for Microsoft 365 spo homesite set command to set the specified communication site as the Home Site.
m365 login
m365 spo homesite set --siteUrl https://<tenant>.sharepoint.com/sites/<communicationsite>
Points to remember
Only one communication site can be set as the home site.
Search scope for the site will be changed to tenant-wide search.
The site will be automatically set up as an organization news site.
The first time you set up a home site, it might take up to several minutes for the changes to take effect.
If you run the above command again to switch your home site to a different site, it might take up to 2 hours.
Home site can be registered as a hub site, but it can’t be associated with a hub.
Unregister a home site from your tenant
If you have registered a site as a home site in your tenant previously and now you don’t want to have any home site in your tenant, you need to run the following PowerShell command with administrator privileges:
Remove-SPOHomeSite
This removes the current SharePoint Online Home Site setting. Note that you do not need to specify the URL of your home site.
In my previous blog about Commenting in SharePoint Online and Microsoft lists, I explained where you can find the comments options, what are the permission considerations, working with commenting using SharePoint REST APIs and JSON formatting, etc. In this blog I will explain how you can enable/disable the commenting in SharePoint Online/Microsoft Lists.
Commenting in lists is a great feature which will help many organizations. However, it’s possible that some organizations may want to disable this feature as they already have some mechanism in place for commenting, for example approvals system as mentioned here.
Currently it is not possible to disable commenting at the SharePoint site or list level (possible as of June 2021). Microsoft is working on the new feature which will allow users to enable/disable the comments for individual SharePoint lists.
However, Admins can enable/disable this feature at the organization level by changing the CommentsOnListItemsDisabled parameter in the Set-SPOTenant PowerShell cmdlet:
# To disable comments on list items
Connect-SPOService -Url https://<tenant>-admin.sharepoint.com/
Set-SPOTenant -CommentsOnListItemsDisabled $true
# To enable comments on list items
Connect-SPOService -Url https://<tenant>-admin.sharepoint.com/
Set-SPOTenant -CommentsOnListItemsDisabled $false
Replace <tenant> with the name of your Microsoft 365 tenant.
Using PnP PowerShell
You can also use PnP PowerShell to enable or disable commenting in SharePoint Online/Microsoft Lists at tenant level:
# Connect to SharePoint online admin center
Connect-PnPOnline -Url https://<tenant>-admin.sharepoint.com/ -Interactive
# To disable comments on list items
Set-PnPTenant -CommentsOnListItemsDisabled $true
# To enable comments on list items
Set-PnPTenant -CommentsOnListItemsDisabled $false
Using CLI for Microsoft 365
Use below CLI for Microsoft 365 script to enable or disable commenting in SharePoint Online/Microsoft Lists at tenant level:
# Get Credentials to connect
$m365Status = m365 status
if ($m365Status -match "Logged Out") {
m365 login
}
# To disable comments on list items
m365 spo tenant settings set --CommentsOnListItemsDisabled true
# To enable comments on list items
m365 spo tenant settings set --CommentsOnListItemsDisabled false
Note: You must be a SharePoint Administrator or Global Administrator in your tenant to enable/disable this feature using PowerShell.
I hope you liked this blog. Give your valuable feedback & suggestions in the comments section below and share this blog with others.
Connexion
