|
| 1 | +--- |
| 2 | +external help file: Microsoft.Exchange.ServerStatus-Help.xml |
| 3 | +online version: https://learn.microsoft.com/powershell/module/exchange/set-exchangefeature |
| 4 | +applicable: Exchange Server 2019 |
| 5 | +title: Set-ExchangeFeature |
| 6 | +schema: 2.0.0 |
| 7 | +author: lusassl-msft |
| 8 | +ms.author: lusassl |
| 9 | +ms.reviewer: srvar |
| 10 | +--- |
| 11 | + |
| 12 | +# Set-ExchangeFeature |
| 13 | + |
| 14 | +## SYNOPSIS |
| 15 | +This cmdlet is available only in on-premises Exchange. |
| 16 | + |
| 17 | +Use the Set-ExchangeFeature cmdlet to approve or block features flighted via Feature Flighting on Exchange Server. |
| 18 | + |
| 19 | +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). |
| 20 | + |
| 21 | +## SYNTAX |
| 22 | + |
| 23 | +``` |
| 24 | +Set-ExchangeFeature [-Approve] |
| 25 | + [-Block] |
| 26 | + [-FeatureID <Microsoft.Exchange.Data.MultiValuedProperty`1[System.String]>] |
| 27 | + [-Identity] <ServerIdParameter>] |
| 28 | +``` |
| 29 | + |
| 30 | +## DESCRIPTION |
| 31 | +The Set-ExchangeFeature cmdlet lets you approve or block features flighted via Feature Flighting, a service introduced in the Exchange Server 2019 CU15 (2025H1) update. |
| 32 | + |
| 33 | +You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). |
| 34 | + |
| 35 | +## EXAMPLES |
| 36 | + |
| 37 | +### Example 1 |
| 38 | +```powershell |
| 39 | +PS C:\> Set-ExchangeFeature -Identity ex01.contoso.com -FeatureID @("F1.1.1") -Approve |
| 40 | +``` |
| 41 | + |
| 42 | +This command approves the feature F1.1.1 on the computer named ex01.contoso.com. |
| 43 | + |
| 44 | +### Example 2 |
| 45 | +```powershell |
| 46 | +PS C:\> Set-ExchangeFeature -Identity ex01.contoso.com -FeatureID @("F1.1.1", "F1.2.1", "F2.1.1") -Approve |
| 47 | +``` |
| 48 | + |
| 49 | +This command approves the features F1.1.1, F1.2.1, and F2.1.1 on the computer named ex01.contoso.com. |
| 50 | + |
| 51 | +### Example 3 |
| 52 | +```powershell |
| 53 | +PS C:\> Set-ExchangeFeature -Identity ex01.contoso.com -FeatureID @("F1.1.1", "F1.2.1", "F2.1.1") -Block |
| 54 | +``` |
| 55 | + |
| 56 | +This command blocks the features F1.1.1, F1.2.1, and F2.1.1 on the computer named ex01.contoso.com. |
| 57 | + |
| 58 | +## PARAMETERS |
| 59 | + |
| 60 | +### -Approve |
| 61 | +The Approve parameter approves the feature specified by the FeatureID parameter. |
| 62 | + |
| 63 | +```yaml |
| 64 | +Type: SwitchParameter |
| 65 | +Parameter Sets: (All) |
| 66 | +Aliases: |
| 67 | + |
| 68 | +Required: False |
| 69 | +Position: Named |
| 70 | +Default value: None |
| 71 | +Accept pipeline input: False |
| 72 | +Accept wildcard characters: False |
| 73 | +``` |
| 74 | +
|
| 75 | +### -Block |
| 76 | +he Block parameter blocks the feature specified by the FeatureID parameter. |
| 77 | +
|
| 78 | +```yaml |
| 79 | +Type: SwitchParameter |
| 80 | +Parameter Sets: (All) |
| 81 | +Aliases: |
| 82 | + |
| 83 | +Required: False |
| 84 | +Position: Named |
| 85 | +Default value: None |
| 86 | +Accept pipeline input: False |
| 87 | +Accept wildcard characters: False |
| 88 | +``` |
| 89 | +
|
| 90 | +### -FeatureID |
| 91 | +The FeatureID parameter specifies the feature you want to control. |
| 92 | +
|
| 93 | +```yaml |
| 94 | +Type: Microsoft.Exchange.Data.MultiValuedProperty`1[System.String] |
| 95 | +Parameter Sets: (All) |
| 96 | +Aliases: |
| 97 | + |
| 98 | +Required: False |
| 99 | +Position: Named |
| 100 | +Default value: None |
| 101 | +Accept pipeline input: False |
| 102 | +Accept wildcard characters: False |
| 103 | +``` |
| 104 | +
|
| 105 | +### -Identity |
| 106 | +The Identity parameter specifies the Exchange server that you want to modify. You can use any value that uniquely identifies the server. For example: |
| 107 | +
|
| 108 | +- Name |
| 109 | +- FQDN |
| 110 | +- Distinguished name (DN) |
| 111 | +- Exchange Legacy DN |
| 112 | +
|
| 113 | +```yaml |
| 114 | +Type: ServerIdParameter |
| 115 | +Parameter Sets: (All) |
| 116 | +Aliases: |
| 117 | + |
| 118 | +Required: True |
| 119 | +Position: 0 |
| 120 | +Default value: None |
| 121 | +Accept pipeline input: True (ByPropertyName, ByValue) |
| 122 | +Accept wildcard characters: False |
| 123 | +``` |
| 124 | +
|
| 125 | +### CommonParameters |
| 126 | +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). |
| 127 | +
|
| 128 | +## INPUTS |
| 129 | +
|
| 130 | +### Input types |
| 131 | +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. |
| 132 | +
|
| 133 | +## OUTPUTS |
| 134 | +
|
| 135 | +### Output types |
| 136 | +To see the return types, which are also known as output types, that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Output Type field is blank, the cmdlet doesn't return data. |
| 137 | +
|
| 138 | +## NOTES |
| 139 | +
|
| 140 | +## RELATED LINKS |
0 commit comments