Search Results for

    Show / Hide Table of Contents

    Set-PnPTermGroup

    SYNOPSIS

    Updates an existing term group.

    SYNTAX

    Set-PnPTermGroup -Identity <TaxonomyTermGroupPipeBind> [-Name <String>] [-Description <String>] 
     [-TermStore <TaxonomyTermStorePipeBind>] [-Connection <PnPConnection>] 
    

    DESCRIPTION

    The cmdlet allows you to update an existing term group.

    EXAMPLES

    Example 1

    Set-PnPTermGroup -Identity "Departments" -Name "Company Units"
    

    Renames the Departments termgroup to "Company Units".

    PARAMETERS

    -Description

    Optional description of the term group.

    Type: String
    Parameter Sets: (All)
    Aliases:
    
    Required: False
    Position: Named
    Default value: None
    Accept pipeline input: False
    Accept wildcard characters: False
    

    -Identity

    The term group to update. Either name or a GUID.

    Type: TaxonomyTermGroupPipeBind
    Parameter Sets: (All)
    Aliases:
    
    Required: True
    Position: 0
    Default value: None
    Accept pipeline input: True (ByValue)
    Accept wildcard characters: False
    

    -Name

    The new name for the term group.

    Type: String
    Parameter Sets: (All)
    Aliases:
    
    Required: False
    Position: Named
    Default value: None
    Accept pipeline input: False
    Accept wildcard characters: False
    

    -TermStore

    The termstore to use. If not specified the default term store is used.

    Type: TaxonomyTermStorePipeBind
    Parameter Sets: (All)
    Aliases:
    
    Required: False
    Position: Named
    Default value: None
    Accept pipeline input: False
    Accept wildcard characters: False
    

    -Connection

    Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection.

    Type: PnPConnection
    Parameter Sets: (All)
    
    Required: False
    Position: Named
    Default value: None
    Accept pipeline input: False
    Accept wildcard characters: False
    

    RELATED LINKS

    Microsoft 365 Patterns and Practices

    Back to top Generated by DocFX spacer