You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise.md
+9-5Lines changed: 9 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -58,8 +58,8 @@ To set up the audit log stream, follow the instructions for your provider:
@@ -213,7 +213,7 @@ From {% data variables.product.prodname_dotcom %}:
213
213
214
214
### Setting up streaming to Azure Event Hubs
215
215
216
-
> [!NOTE]
216
+
> [!NOTE]
217
217
> - Event Hubs instances in Azure Government are not supported.
218
218
> - With **{% data variables.enterprise.data_residency %},** audit log streaming to Azure Event Hubs is not supported with IP Firewall rules enabled.
219
219
@@ -270,6 +270,8 @@ To set up streaming to Google Cloud Storage, create a service account in Google
270
270
1. To verify that {% data variables.product.prodname_dotcom %} can connect and write to the Google Cloud Storage bucket, click **Check endpoint**.
271
271
{% data reusables.enterprise.verify-audit-log-streaming-endpoint %}
272
272
273
+
{% ifversion ghec %}
274
+
273
275
### Setting up streaming to Microsoft Purview
274
276
275
277
{% data reusables.copilot.agent-session-streaming-availability-note %}
@@ -284,6 +286,8 @@ To set up streaming to Microsoft Purview, configure streaming in {% data variabl
284
286
1. Click **Authorize with Entra**.
285
287
1. When you're redirected to Microsoft Entra, add the {% data variables.product.github %} app and authorize it for your tenant.
286
288
289
+
{% endif %}
290
+
287
291
### Setting up streaming to Splunk
288
292
289
293
To stream audit logs to Splunk's HTTP Event Collector (HEC) endpoint, make sure that the endpoint is configured to accept HTTPS connections. See [Set up and use HTTP Event Collector in Splunk Web](https://docs.splunk.com/Documentation/Splunk/latest/Data/UsetheHTTPEventCollector) in the Splunk documentation.
@@ -355,8 +359,8 @@ To restart streaming, click **Resume stream**.
355
359
{% data reusables.copilot.agent-session-streaming-availability-note %}
356
360
357
361
{% data reusables.enterprise-accounts.access-enterprise %}
358
-
1. At the top of the page, click AI Controls
359
-
1. Under "Copilot", select **Enabled everywhere** for "Copilot Usage Records Streaming"
362
+
1. At the top of the page, click AI Controls
363
+
1. Under "Copilot", select **Enabled everywhere** for "Copilot Usage Records Streaming"
360
364
1. Configure a streaming destination. See [Setting up audit log streaming](#setting-up-audit-log-streaming).
361
365
362
366
You can also retrieve {% data variables.product.prodname_copilot_short %} usage data through the REST API by selecting **Enabled everywhere** for "Copilot Usage Records API". See [AUTOTITLE](/rest/copilot/copilot-usage-metrics#get-copilot-usage-records-for-an-enterprise).
# `CODE_SIGNING_REQUIRED=NO` and `CODE_SIGNING_ALLOWED=NO`: turn off code signing, which may fail with CodeQL
302
+
# `COMPILATION_CACHE_ENABLE_CACHING=NO` and `SWIFT_ENABLE_COMPILE_CACHE=NO`: turn off build caching, which may skip compilation steps
303
+
# `SWIFT_USE_INTEGRATED_DRIVER=NO`: turn off the Swift integrated driver, which is incompatible with CodeQL
304
+
codeql database create -l swift \
305
+
-c "xcodebuild build -target your-target
306
+
CODE_SIGNING_REQUIRED=NO
307
+
CODE_SIGNING_ALLOWED=NO
308
+
COMPILATION_CACHE_ENABLE_CACHING=NO
309
+
SWIFT_ENABLE_COMPILE_CACHE=NO
310
+
SWIFT_USE_INTEGRATED_DRIVER=NO" \
311
+
swift-database
301
312
```
302
313
303
314
You can pass the `archive` and `test` options to `xcodebuild`. However, the standard `xcodebuild` command is recommended as it should be the fastest, and should be all that {% data variables.product.prodname_codeql %} requires for a successful scan.
Copy file name to clipboardExpand all lines: content/copilot/reference/ai-models/model-hosting.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -87,8 +87,9 @@ When using {% data variables.copilot.copilot_gemini %} models, input prompts and
87
87
Used for:
88
88
89
89
* {% data variables.copilot.copilot_grok_45 %}
90
+
* {% data variables.copilot.copilot_grok_46 %}
90
91
91
-
These models are hosted on xAI. xAI operates {% data variables.copilot.copilot_grok_45 %} in {% data variables.product.prodname_copilot %} under a zero data retention API policy. This means xAI commits that user content (both inputs sent to the model and outputs generated by the model):
92
+
These models are hosted on xAI. xAI operates these models in {% data variables.product.prodname_copilot %} under a zero data retention API policy. This means xAI commits that user content (both inputs sent to the model and outputs generated by the model):
@@ -48,7 +48,7 @@ In {% data variables.copilot.copilot_cli_short %}, the `sandbox` key is an excep
48
48
49
49
For server-managed deployments, the enterprise can apply different governance to groups of users based on their enterprise team membership. The enterprise defines all settings—team membership only determines which users receive a given set of values.
50
50
51
-
To make a key eligible for team-specific values, mark it as overridable in `{% data variables.copilot.managed_setting_file %}` using the `{ "overridable": <VALUE> }` syntax. An overridable key uses the team's value when set, or falls back to your enterprise default when the team leaves it unset. The `{ "overridable": <VALUE> }` syntax applies to the `permissions.model`, `permissions.disableBypassPermissionsMode`, `allowedMcpServers`, and `deniedMcpServers` keys. Keys not marked overridable remain an enterprise-level decision that teams can't modify.
51
+
To make a key eligible for team-specific values, mark it as overridable in `{% data variables.copilot.managed_setting_file %}` using the `{ "overridable": <VALUE> }` syntax. An overridable key uses the team's value when set, or falls back to your enterprise default when the team leaves it unset. The `{ "overridable": <VALUE> }` syntax applies to the `model`, `permissions.disableBypassPermissionsMode`, `allowedMcpServers`, and `deniedMcpServers` keys. Keys not marked overridable remain an enterprise-level decision that teams can't modify.
52
52
53
53
`enabledPlugins` and `extraKnownMarketplaces` work additively. The enterprise `{% data variables.copilot.managed_setting_file %}` sets a baseline, and an enterprise team file can add more plugins and marketplaces on top of it. For the full setup steps, see [AUTOTITLE](/copilot/how-tos/administer-copilot/manage-for-enterprise/manage-agents/configure-enterprise-managed-settings#overriding-settings-for-specific-teams).
54
54
@@ -58,9 +58,9 @@ The following example shows these keys in one managed settings file.
58
58
59
59
```json
60
60
{
61
+
"model": "auto",
61
62
"permissions": {
62
-
"disableBypassPermissionsMode": "disable",
63
-
"model": "auto"
63
+
"disableBypassPermissionsMode": "disable"
64
64
},
65
65
"enabledPlugins": {
66
66
"my-plugin@agent-skills": true
@@ -148,6 +148,13 @@ Restricts plugin installation to only the marketplaces explicitly defined by the
Sets auto model selection as the default for new conversations. See [AUTOTITLE](/copilot/concepts/models/auto-model-selection).
154
+
155
+
* When you set `model` to `"auto"`, new sessions use Auto model unless the user specifies a different model on a per-conversation basis.
156
+
* This key is overridable by enterprise team mapping. In your `{% data variables.copilot.managed_setting_file %}`, use the `{ "overridable": "auto" }` syntax to specialize the key's configuration on a per-team basis. You can then set `"model": "unmanaged"` in a team settings file, providing a specialization that takes precedence over `{% data variables.copilot.managed_setting_file %}` for members of the subject team.
157
+
151
158
## permissions
152
159
153
160
### disableBypassPermissionsMode
@@ -161,13 +168,6 @@ When you set `disableBypassPermissionsMode` to `"disable"`, users cannot turn on
161
168
* In the {% data variables.copilot.github_copilot_app %}, the "Allow all" setting for "Tool Permissions" is blocked in the sessions settings.
162
169
* This key is overridable by enterprise team mapping. In your `{% data variables.copilot.managed_setting_file %}`, use the `{ "overridable": "disable" }` syntax to specialize the key's configuration on a per-team basis. You can then set `"disableBypassPermissionsMode": "unmanaged"` in a team settings file, providing a specialization that takes precedence over `{% data variables.copilot.managed_setting_file %}` for members of the subject team.
163
170
164
-
### model
165
-
166
-
Sets auto model selection as the default for new conversations. See [AUTOTITLE](/copilot/concepts/models/auto-model-selection).
167
-
168
-
* When you set `permissions.model` to `"auto"`, new sessions use Auto model unless the user specifies a different model on a per-conversation basis.
169
-
* This key is overridable by enterprise team mapping. In your `{% data variables.copilot.managed_setting_file %}`, use the `{ "overridable": "auto" }` syntax to specialize the key's configuration on a per-team basis. You can then set `"model": "unmanaged"` in a team settings file, providing a specialization that takes precedence over `{% data variables.copilot.managed_setting_file %}` for members of the subject team.
170
-
171
171
## telemetry
172
172
173
173
Configures OpenTelemetry export, routing {% data variables.product.prodname_copilot_short %} usage data to a collector of your choice.
2-64 vCPU Ubuntu and Windows runners are supported with Azure VNET. For more information on these runner types, see [AUTOTITLE](/actions/reference/runners/larger-runners#specifications-for-general-larger-runners).
1
+
Azure VNET private networking is only available for larger runners (2-64 vCPU Ubuntu and Windows). Standard {% data variables.product.company_short %}-hosted runners are not supported. For more information on larger runner types, see [AUTOTITLE](/actions/reference/runners/larger-runners#specifications-for-general-larger-runners).
2
2
3
3
{% data reusables.actions.static-ip-limitation-vnet %} You must use dynamic IP addresses, which is the default configuration for larger runners. For more information about networking for larger runners, see [AUTOTITLE](/actions/reference/runners/larger-runners#networking-for-larger-runners).
0 commit comments