Skip to content

Commit f233ba5

Browse files
authored
Update boundary-groups.md
1 parent 75eced2 commit f233ba5

1 file changed

Lines changed: 4 additions & 1 deletion

File tree

memdocs/configmgr/core/servers/deploy/configure/boundary-groups.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -104,8 +104,11 @@ To manage fallback to the default site boundary group:
104104

105105
- Open the properties of a custom boundary group. Change the values for the explicit link to a default site boundary group. When you set a new time in minutes for fallback or block fallback, that change affects only the link you're configuring. Configuration of the explicit link overrides the settings on the **Default Behavior** tab of a default site boundary group.
106106

107-
### Default site boundary group behavior supports cloud source selection
107+
## Default site boundary group behavior supports cloud source selection
108108
<!--10674394-->
109+
110+
*(Added in version 2207)*
111+
109112
You can add options via PowerShell to include and prefer cloud management gateway (CMG) management points for the default site boundary group. When a site is set up, there's a default site boundary group created for each site and all the clients are by default mapped to it until they're assigned to some custom boundary group.
110113

111114
Currently on the admin console, you can add references to default site boundary group, but the added references don't have any effect when the client requests for management point list. Starting with technical preview version 2206, you can use PowerShell cmdlets to include and prefer cloud-based sources for clients in the default site boundary group. This action is currently only for the management point role.

0 commit comments

Comments
 (0)