Skip to content

Commit a93d6f5

Browse files
authored
Merge branch 'MicrosoftDocs:main' into Broken-link-fix-balapv
2 parents 5eeeaa5 + bca8794 commit a93d6f5

File tree

8 files changed

+87
-10
lines changed

8 files changed

+87
-10
lines changed
57.2 KB
Loading
54.2 KB
Loading
80.2 KB
Loading
54 KB
Loading
Lines changed: 75 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,75 @@
1+
---
2+
title: Send your Azure VMware Solution logs to Log Analytics
3+
description: Learn about sending logs to log analytics.
4+
ms.topic: how-to
5+
ms.service: azure-vmware
6+
ms.date: 11/15/2022
7+
---
8+
9+
# Send your Azure VMware Solution logs to Log Analytics
10+
11+
This article shows you how to send Azure VMware Solution logs to Azure Monitor Log Analytics. You can send logs from your AVS private cloud to your Log Analytics workspace, allowing you to take advantage of the Log Analytics feature set, including:
12+
13+
• Powerful querying capabilities with Kusto Query Language (KQL)
14+
15+
• Interactive report-creation capability based on your data, using Workbooks
16+
17+
...without having to get your logs out of the Microsoft ecosystem!
18+
19+
In the rest of this article, we’ll show you how easy it is to make this happen.
20+
21+
## How to set up Log Analytics
22+
23+
A Log Analytics workspace:
24+
25+
• Contains your AVS private cloud logs.
26+
27+
• Is the workspace from which you can take desired actions, such as querying for logs.
28+
29+
In this section, you’ll:
30+
31+
• Configure a Log Analytics workspace
32+
33+
• Create a diagnostic setting in your private cloud to send your logs to this workspace
34+
35+
### Create a resource
36+
37+
1. In the Azure portal, go to **Create a resource**.
38+
2. Search for “Log Analytics Workspace” and click **Create** -> **Log Analytics Workspace**.
39+
40+
:::image type="content" source="media/send-logs-to-log-analytics/marketplace.png" alt-text="Screenshot of Create a resource.":::
41+
42+
### Set up your workspace
43+
44+
1. Enter the Subscription you intend to use, the Resource Group that’ll house this workspace. Give it a name and select a region.
45+
1. Click **Review** + **Create**.
46+
47+
:::image type="content" source="media/send-logs-to-log-analytics/create-workspace.png" alt-text="Screenshot of Marketplace.":::
48+
49+
### Add a diagnostic setting
50+
51+
Next, we add a diagnostic setting in your AVS private cloud, so it knows where to send your logs to.
52+
53+
:::image type="content" source="media/send-logs-to-log-analytics/private-cloud.png" alt-text="Screenshot of vh-private-cloud.":::
54+
55+
1. Click your AVS private cloud.
56+
Go to Diagnostic settings on the left-hand menu under Monitoring.
57+
Select **Add diagnostic setting**.
58+
2. Give your diagnostic setting a name.
59+
Select the log categories you are interested in sending to your Log Analytics workspace.
60+
61+
3. Make sure to select the checkbox next to **Send to Log Analytics workspace**.
62+
Select the Subscription your Log Analytics workspace lives in and the Log Analytics workspace.
63+
Click **Save** on the top left.
64+
65+
:::image type="content" source="media/send-logs-to-log-analytics/diagnostic-setting.png" alt-text="Screenshot of Diagnostics settings.":::
66+
67+
At this point, your Log Analytics workspace has been successfully configured to receive logs from your AVS private cloud.
68+
69+
## Search and analyze logs using Kusto
70+
71+
Now that you’ve successfully configured your logs to go to your Log Analytics workspace, you can use that data to gain meaningful insights with Log Analytics’ search feature.
72+
Log Analytics uses a language called the Kusto Query Language (or Kusto) to search through your logs.
73+
74+
For more information, see
75+
[Data analysis in Azure Data Explorer with Kusto Query Language](/training/paths/data-analysis-data-explorer-kusto-query-language/).

articles/azure-vmware/toc.yml

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -180,6 +180,8 @@
180180
href: rotate-cloudadmin-credentials.md
181181
- name: Save costs with a reserved instance
182182
href: reserved-instance.md
183+
- name: Send logs to log analytics
184+
href: send-logs-to-log-analytics.md
183185
- name: Partner solution ecosystem
184186
items:
185187
- name: Operating system support for VMs
@@ -196,6 +198,8 @@
196198
href: ecosystem-app-monitoring-solutions.md
197199
- name: Bitnami appliance deployment
198200
href: bitnami-appliances-deployment.md
201+
- name: Send logs to Log Analytics
202+
href: send-logs-to-log-analytics.md
199203
- name: VMware solutions
200204
items:
201205
- name: Configure HCX network extension

articles/virtual-desktop/remote-app-streaming/licensing.md

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: virtual-desktop
55
author: Heidilohr
66
ms.service: virtual-desktop
77
ms.topic: conceptual
8-
ms.date: 04/27/2022
8+
ms.date: 11/17/2022
99
ms.author: helohr
1010
manager: femila
1111
---
@@ -70,6 +70,12 @@ Here's a summary of the two types of licenses for Azure Virtual Desktop you can
7070

7171
The Azure Virtual Desktop per-user access license isn't a full replacement for a Windows or Microsoft 365 license. Per-user licenses only grant access rights to Azure Virtual Desktop and don't include Microsoft Office, Microsoft 365 Defender, or Universal Print. This means that if you choose a per-user license, you'll need to separately license other products and services to grant your users access to them in your Azure Virtual Desktop environment.
7272

73+
There are a few ways to enable your external users to access Office:
74+
75+
- Users can sign in to Office with their own Office account.
76+
- You can re-sell Office through your Cloud Service Provider (CSP).
77+
- You can distribute Office by using a Service Provider Licensing Agreement (SPLA).
78+
7379
## Next steps
7480

7581
Now that you're familiar with your licensing pricing options, you can start planning your Azure Virtual Desktop environment. Here are some articles that might help you:

articles/virtual-desktop/remote-app-streaming/per-user-access-pricing.md

Lines changed: 1 addition & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ author: Heidilohr
66

77
ms.service: virtual-desktop
88
ms.topic: how-to
9-
ms.date: 10/31/2022
9+
ms.date: 11/17/2022
1010
ms.author: helohr
1111
manager: femila
1212
---
@@ -39,14 +39,6 @@ To enroll your Azure subscription into per-user access pricing:
3939

4040
7. After enrollment is done, check the value in the **Per-user access pricing** column of the subscriptions list to make sure it's changed from “Enrolling” to “Enrolled.”
4141

42-
## Licensing other products and services for use with Azure Virtual Desktop
43-
44-
There are a few ways to enable your external users to access Office:
45-
46-
- Users can sign in to Office with their own Office account.
47-
- You can re-sell Office through your Cloud Service Provider (CSP).
48-
- You can distribute Office by using a Service Provider Licensing Agreement (SPLA).
49-
5042
## Next steps
5143

5244
To learn more about per-user access pricing, see [Understanding licensing and per-user access pricing](licensing.md). If you want to learn how to estimate per-user app streaming costs for your deployment, see [Estimate per-user app streaming costs for Azure Virtual Desktop](streaming-costs.md). For estimating total deployment costs, see [Understanding total Azure Virtual Desktop deployment costs](total-costs.md).

0 commit comments

Comments
 (0)