This post shows how to create a term in a SharePoint taxonomy term set using Power Automate and the SharePoint REST API v2.1. It is useful when you want to automate adding a managed metadata term based on your scenario. What you need A SharePoint site with either site level or tenant level term store The term group ID for the site-level or tenant level term group The term set ID for the destination term set A Power Automate flow trigger such as item-created or manual trigger Step 1: Get the term group and term set IDs In SharePoint, go to Site Settings > Term Store Management.

This post provides a PowerShell script to import synonyms (labels) into a SharePoint term set using the PnP.PowerShell module. The sample using PnP PowerShell to import a csv file (same format you would use for import via UI for a term set but with an additional column for Synonyms delimited by |) Prerequisites Install the PnP.PowerShell module (run as an admin): Install-Module PnP.PowerShell -Scope CurrentUser An Azure AD app or other authentication method with sufficient permissions to manage taxonomy/term store, or use interactive Connect-PnPOnline.

Introduction Taxonomy feature is not activated by default in SharePoint sites linked to a private or shared Teams Channels. When attempting to add content types with managed metadata columns, you may encounter an error message stating “Taxonomy disabled”. To resolve this issue, you can enable the taxonomy feature with the ID 73ef14b1-13a9-416b-a9b5-ececa2b0604c using the PowerShell cmdlet Enable-PnPFeature before adding the content types to the sites with the template TEAMCHANNEL#1. Script to check whether feature taxonomy is enabled Get-PnPFeature -Scope Site | Where-Object { $_.