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: articles/bastion/kerberos-authentication-portal.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
@@ -18,7 +18,8 @@ This article shows you how to configure Azure Bastion to use Kerberos authentica
18
18
19
19
* The Kerberos setting for Azure Bastion can be configured in the Azure portal only and not with native client.
20
20
* VMs migrated from on-premises to Azure aren't currently supported for Kerberos.
21
-
* Cross-realm authentication isn't currently supported for Kerberos.
21
+
* Cross-realm authentication isn't currently supported for Kerberos.
22
+
* The Domain controller must be an Azure Hosted VM within the same VNET that bastion is deployed.
22
23
* Changes to DNS server aren't currently supported for Kerberos. After making any changes to DNS server, you'll need to delete and re-create the Bastion resource.
23
24
* If additional DC (domain controllers) are added, Bastion will only recognize the first DC.
24
25
* If additional DCs are added for different domains, the added domains can't successfully authenticate with Kerberos.
Copy file name to clipboardExpand all lines: articles/communication-services/concepts/analytics/enable-logging.md
+10-3Lines changed: 10 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -51,11 +51,11 @@ You'll then be prompted to choose a name for your Diagnostic Setting, which is u
51
51
52
52
## Choose Destinations
53
53
54
-
You'll also be prompted to select a destination to store the logs. Platform logs and metrics can be sent to the destinations in the following table, which is also included in Azure Monitor documentation in deeper detail: [Create diagnostic settings to send platform logs and metrics to different destinations](../../../azure-monitor/essentials/diagnostic-settings.md?tabs=CMD)
54
+
You'll also be prompted to select a destination to store the logs. Platform logs and metrics can be sent to the destinations in the following table, which is also included in Azure Monitor documentation in deeper detail: [Create diagnostic settings to send platform logs and metrics to different destinations.](../../../azure-monitor/essentials/diagnostic-settings.md?tabs=CMD)
55
55
56
56
| Destination | Description |
57
57
|:------------|:------------|
58
-
|[Log Analytics workspace](../../../azure-monitor/logs/log-analytics-workspace-overview.md)| Sending logs and metrics to a Log Analytics workspace allows you to analyze them with other monitoring data collected by Azure Monitor using powerful log queries and also to use other Azure Monitor features such as alerts and visualizations. |
58
+
|[Log Analytics workspace](../../../azure-monitor/logs/log-analytics-workspace-overview.md)| Sending logs and metrics to a Log Analytics workspace allows you to analyze them with other monitoring data collected by Azure Monitor using powerful log queries and also to use other Azure Monitor features such as alerts and visualizations. <br><br> If you don't have a Log Analytics workspace to send your data to, you must [create one before you proceed.](../../../azure-monitor/logs/quick-create-workspace.md)|
59
59
|[Event Hubs](../../../event-hubs/index.yml)| Sending logs and metrics to Event Hubs allows you to stream data to external systems such as third-party SIEMs and other log analytics solutions. |
60
60
|[Azure storage account](../../../storage/blobs/index.yml)| Archiving logs and metrics to an Azure storage account is useful for audit, static analysis, or backup. Compared to Azure Monitor Logs and a Log Analytics workspace, Azure storage is less expensive and logs can be kept there indefinitely. |
61
61
@@ -67,6 +67,13 @@ They're all viable and flexible options that can adapt to your specific storage
67
67
68
68
## Log Analytics Workspace for additional analytics features
69
69
70
-
By choosing to send your logs to a [Log Analytics workspace](../../../azure-monitor/logs/log-analytics-overview.md) destination, you enable more features within Azure Monitor generally and for your Communications Services. Log Analytics is a tool within Azure portal used to create, edit, and run [queries](../../../azure-monitor/logs/queries.md) with data in your Azure Monitor logs and metrics and [Workbooks](../../../azure-monitor/visualize/workbooks-overview.md), [alerts](../../../azure-monitor/alerts/alerts-log.md), [notification actions](../../../azure-monitor/alerts/action-groups.md), [REST API access](/rest/api/loganalytics/), and many others.
70
+
By choosing to send your logs to a [Log Analytics workspace](../../../azure-monitor/logs/log-analytics-overview.md) destination, you enable more features within Azure Monitor generally and for your Communications Services. Log Analytics is a tool within Azure portal used to create, edit, and run [queries](../../../azure-monitor/logs/queries.md) with data in your Azure Monitor logs and metrics and [Workbooks](../../../azure-monitor/visualize/workbooks-overview.md), [alerts](../../../azure-monitor/alerts/alerts-log.md), [notification actions](../../../azure-monitor/alerts/action-groups.md), [REST API access](/rest/api/loganalytics/), and many others. If you don't have a Log Analytics workspace, you must [create one before you proceed.](../../../azure-monitor/logs/quick-create-workspace.md)
71
71
72
72
For your Communications Services logs, we've provided a useful [default query pack](../../../azure-monitor/logs/query-packs.md#default-query-pack) to provide an initial set of insights to quickly analyze and understand your data. These query packs are described here: [Log Analytics for Communications Services](query-call-logs.md).
73
+
74
+
## Next Steps
75
+
76
+
- If you don't have a Log Analytics workspace to send your data to, you must create one before you proceed. See: [Create a Log Analytics workspace](../../../azure-monitor/logs/quick-create-workspace.md)
77
+
78
+
79
+
- You may start a Diagnostic Setting to use certain capabilities by enabling collection for all logs, however you should monitor costs associated with logs from Diagnostic Settings, see: [Controlling costs](../../../azure-monitor/essentials/diagnostic-settings.md#controlling-costs)
- Follow instructions to add diagnostic settings for your resource here [Enable logs via Diagnostic Settings in Azure Monitor.](../analytics/enable-logging.md) When prompted to select [select logs](../analytics/enable-logging.md#adding-a-diagnostic-setting) select "**allLogs**".
193
-
- If you have multiple Azure Communications Services Resource IDs you must enable these settings for each resource ID and query call details for participants within their respective Azure Communications Services Resource ID. Your data volume, retention, and CDC query usage in Log Analytics is billed through existing Azure data meters, monitor your data usage and retention policies for [cost considerations as needed](../../../azure-monitor/logs/cost-logs.md)
192
+
- Follow instructions to add diagnostic settings for your resource here [Enable logs via Diagnostic Settings in Azure Monitor.](../analytics/enable-logging.md)We recommend you initially collect all logs and then determine which logs you want to retain and for how long after you have an understanding of the capabilities in Azure Monitor. When adding your diagnostic setting you will be prompted to [select logs](../analytics/enable-logging.md#adding-a-diagnostic-setting), select "**allLogs**" to collect all logs. Your data volume, retention, and Call Diagnostics query usage in Log Analytics within Azure Monitor is billed through existing Azure data meters. You should monitor your data usage and retention policies for [cost considerations as needed](../../../azure-monitor/logs/cost-logs.md). Also see: [Controlling costs.](../../../azure-monitor/essentials/diagnostic-settings.md#controlling-costs)
193
+
- If you have multiple Azure Communications Services Resource IDs you must enable these settings for each resource ID and query call details for participants within their respective Azure Communications Services Resource ID.
194
194
195
195
- If Azure Communication Services participants join from different Azure Communication Services Resources, how will they display in Call Diagnostics?
Copy file name to clipboardExpand all lines: articles/defender-for-cloud/tutorial-enable-cspm-plan.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -80,6 +80,8 @@ Once the Defender CSPM plan is enabled on your subscription, you have the abilit
80
80
81
81
1. Select **Continue**.
82
82
83
+
For code to cloud contextualization capabilities and automated developer remediation workflows that come with your DCSPM plan at no additional cost, [connect your DevOps environments](defender-for-devops-introduction.md) to Defender for Cloud.
0 commit comments