|
| 1 | +--- |
| 2 | +external help file: Microsoft.Exchange.TransportMailflow-Help.xml |
| 3 | +online version: https://learn.microsoft.com/powershell/module/exchange/set-arcconfig |
| 4 | +applicable: Exchange Online |
| 5 | +title: Set-ArcConfig |
| 6 | +schema: 2.0.0 |
| 7 | +author: chrisda |
| 8 | +ms.author: chrisda |
| 9 | +ms.reviewer: |
| 10 | +--- |
| 11 | + |
| 12 | +# Set-ArcConfig |
| 13 | + |
| 14 | +## SYNOPSIS |
| 15 | +This cmdlet is available only in the cloud-based service. |
| 16 | + |
| 17 | +Use the Set-ArcConfig cmdlet to modify the list of trusted Authenticated Received Chain (ARC) sealers that are configured in the cloud-based organization. |
| 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 | + |
| 22 | +## SYNTAX |
| 23 | + |
| 24 | +``` |
| 25 | +Set-ArcConfig [-Identity] <HostedConnectionFilterPolicyIdParameter> -ArcTrustedSealers <String[]> |
| 26 | + [-Confirm] |
| 27 | + [-WhatIf] |
| 28 | + [<CommonParameters>] |
| 29 | +``` |
| 30 | + |
| 31 | +## DESCRIPTION |
| 32 | +Services that modify message content in transit before delivery can invalidate DKIM email signatures and affect the authentication of the message. These services can use ARC to provide details of the original authentication before the modifications occurred. Your organization can then trust these details to help authenticate the message. |
| 33 | + |
| 34 | +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). |
| 35 | + |
| 36 | +## EXAMPLES |
| 37 | + |
| 38 | +### Example 1 |
| 39 | +```powershell |
| 40 | +Set-ArcConfig -Identity Default -ArcTrustedSealers fabrikam.com |
| 41 | +``` |
| 42 | + |
| 43 | +This example configures "fabrikam.com" as the only trusted ARC sealer in the organization. |
| 44 | + |
| 45 | +### Example 2 |
| 46 | +```powershell |
| 47 | +$DomainsAdd = @(Get-ArcConfig | select -Expand ArcTrustedSealers) |
| 48 | +
|
| 49 | +$DomainsAdd += "cohovineyard.com","tailspintoys.com" |
| 50 | +
|
| 51 | +Set-ArcConfig -Identity Default -ArcTrustedSealers $DomainsAdd |
| 52 | +``` |
| 53 | + |
| 54 | +This example adds the trusted ARC sealers "cohovineyard.com" and "tailspintoys.com" without affecting the other trusted ARC sealer entries. |
| 55 | + |
| 56 | +### Example 3 |
| 57 | +```powershell |
| 58 | +$x = @(Get-ArcConfig | select -Expand ArcTrustedSealers) |
| 59 | +
|
| 60 | +$y = $x.Split(",") |
| 61 | +
|
| 62 | +$DomainsRemove = [System.Collections.ArrayList]($y) |
| 63 | +
|
| 64 | +$DomainsRemove |
| 65 | +
|
| 66 | +$DomainsRemove.RemoveAt(6) |
| 67 | +
|
| 68 | +Set-ArcConfig -Identity Default -ArcTrustedSealers $DomainsRemove |
| 69 | +``` |
| 70 | + |
| 71 | +This example modifies the trusted ARC sealers list by removing an existing ARC sealer without affecting other ARC sealers that are already specified. |
| 72 | + |
| 73 | +The first four commands return the existing list of ARC sealers. The first ARC sealer in the list has the index number 0, the second has the index number 1, and so on. Use the index number to specify the ARC sealer that you want to remove. |
| 74 | + |
| 75 | +The last two commands remove the seventh ARC sealer that's displayed in the list. |
| 76 | + |
| 77 | +## PARAMETERS |
| 78 | + |
| 79 | +### -Identity |
| 80 | +The Identity parameter specifies the trusted ARC sealers list that you want to modify. Use one of the following values: |
| 81 | + |
| 82 | +- Default for your own organization. |
| 83 | +- \<TenantID\>\Default for delegated organizations. The \<TenantID\> value is a GUID that's visible in many admin portal URLs in Microsoft 365 (the tid= value). For example, a32d39e2-3702-4ff5-9628-31358774c091. |
| 84 | + |
| 85 | +```yaml |
| 86 | +Type: HostedConnectionFilterPolicyIdParameter |
| 87 | +Parameter Sets: (All) |
| 88 | +Aliases: |
| 89 | +Applicable: Exchange Online |
| 90 | + |
| 91 | +Required: True |
| 92 | +Position: 1 |
| 93 | +Default value: None |
| 94 | +Accept pipeline input: True (ByPropertyName, ByValue) |
| 95 | +Accept wildcard characters: False |
| 96 | +``` |
| 97 | +
|
| 98 | +### -ArcTrustedSealers |
| 99 | +The ArcTrustedSealers parameter specifies the domain name of the ARC sealers that you want to add. |
| 100 | +
|
| 101 | +The domain name must match the domain that's shown in the `d` tag in the **ARC-Seal** and **ARC-Message-Signature** headers in affected email messages (for example, fabrikam.com). You can use Outlook to see these headers. |
| 102 | + |
| 103 | +To replace the existing list of ARC sealers with the values you specify, use the syntax `Domain1,Domain2,...DomainN`. To preserve existing values, be sure to include the file types that you want to keep along with the new values that you want to add. |
| 104 | + |
| 105 | +To add or remove file types without affecting the other file type entries, see the Examples section in this topic. |
| 106 | + |
| 107 | +```yaml |
| 108 | +Type: String[] |
| 109 | +Parameter Sets: (All) |
| 110 | +Aliases: |
| 111 | +Applicable: Exchange Online |
| 112 | +
|
| 113 | +Required: True |
| 114 | +Position: Named |
| 115 | +Default value: None |
| 116 | +Accept pipeline input: False |
| 117 | +Accept wildcard characters: False |
| 118 | +``` |
| 119 | + |
| 120 | +### -Confirm |
| 121 | +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. |
| 122 | + |
| 123 | +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. |
| 124 | +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. |
| 125 | + |
| 126 | +```yaml |
| 127 | +Type: SwitchParameter |
| 128 | +Parameter Sets: (All) |
| 129 | +Aliases: cf |
| 130 | +Applicable: Exchange Online |
| 131 | +
|
| 132 | +Required: False |
| 133 | +Position: Named |
| 134 | +Default value: None |
| 135 | +Accept pipeline input: False |
| 136 | +Accept wildcard characters: False |
| 137 | +``` |
| 138 | + |
| 139 | +### -WhatIf |
| 140 | +The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. |
| 141 | + |
| 142 | +```yaml |
| 143 | +Type: SwitchParameter |
| 144 | +Parameter Sets: (All) |
| 145 | +Aliases: wi |
| 146 | +Applicable: Exchange Online |
| 147 | +
|
| 148 | +Required: False |
| 149 | +Position: Named |
| 150 | +Default value: None |
| 151 | +Accept pipeline input: False |
| 152 | +Accept wildcard characters: False |
| 153 | +``` |
| 154 | + |
| 155 | +### CommonParameters |
| 156 | +This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see [about_CommonParameters](https://go.microsoft.com/fwlink/p/?LinkID=113216). |
| 157 | + |
| 158 | +## INPUTS |
| 159 | + |
| 160 | +## OUTPUTS |
| 161 | + |
| 162 | +## NOTES |
| 163 | + |
| 164 | +## RELATED LINKS |
0 commit comments