Merge branch 'main' into patch-3

Author: rjagiewich

exchange/exchange-ps/exchange/Get-IPv6StatusForAcceptedDomain.md

@@ -34,6 +34,11 @@ If IPv6 is enabled for an accepted domain in Exchange Online, IPv4 and IPv6 addr
 
 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).
 
+> [!NOTE]
+> When you use the Enable-IPv6ForAcceptedDomain or Disable-IPv6ForAcceptedDomain cmdlets to update the IPv6 setting for an accepted domain, the updated status can take up to an hour to be visible using Get-IPv6StatusForAcceptedDomain due to caching.
+>
+> For example, Get-IPv6StatusForAcceptedDomain shows the status value Enabled for a domain. You run Disable-IPv6ForAcceptedDomain to disable IPv6 for the domain, you immediately run Get-IPv6StatusForAcceptedDomain to check the staus of the domain, and the command erroneously returns the value Enabled. It might take up to an hour before Get-IPv6StatusForAcceptedDomain shows the correct value Disabled for the domain.
+
 ## EXAMPLES
 
 ### Example 1
@@ -96,10 +101,7 @@ Accept wildcard characters: False
 ### CommonParameters
 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).
 
-## INPUTS
 
-## OUTPUTS
 
-## NOTES
 
-## RELATED LINKS
+

exchange/exchange-ps/exchange/Set-ComplianceSecurityFilter.md

@@ -43,7 +43,7 @@ $filterusers = Get-ComplianceSecurityFilter -FilterName "Ottawa Users Filter"
 
 $filterusers.users.add("pilarp@contoso.com")
 
-Set-ComplianceSecurityFilter -FilterName OttawaUsersFilter -Users $filterusers.users
+Set-ComplianceSecurityFilter -FilterName "Ottawa Users Filter" -Users $filterusers.users
 ```
 
 This example adds user pilarp@contoso.com to the compliance security filter named Ottawa Users Filter without affecting other users assigned to the filter.
@@ -54,7 +54,7 @@ $filterusers = Get-ComplianceSecurityFilter -FilterName "Ottawa Users Filter"
 
 $filterusers.users.remove("annb@contoso.com")
 
-Set-ComplianceSecurityFilter -FilterName OttawaUsersFilter -Users $filterusers.users
+Set-ComplianceSecurityFilter -FilterName "Ottawa Users Filter" -Users $filterusers.users
 ```
 
 This example removes user annb@contoso.com to the compliance security filter named Ottawa Users Filter without affecting other users assigned to the filter.