![]() ![]() It may take a while before any data appears in your Log Analytics workbooks (generally up to 15 minutes) - you will only be seeing fresh data since you linked the data source to Log Analytics. ![]() Click on Workbooks on the left hand menu to access these. Built-In WorkbooksĪzure AD has a good selection of built in workbooks which run off Log Analytics. Select the log categories you want to redirect, and send them to Log Analytics workspace. While we've picked all the categories for this demonstration, make sure you don't pick more than you need as some of the categories can generate a lot of data, and run up the cost. Select all of the log types and direct the data towards your Log Analytics workspace, then click Save. You will notice the Diagnostic Settings screen appears on a lot of different services across Azure, if you want to configure a different service to redirect its logs to Log Analytics it is the same process. Next click Add diagnostic setting to configure the collection of data. Look for an item on the menu called Diagnostic settings and click on it. Once this step has completed, go to the service you wish to link, in this case Azure AD. Go to Azure Portal > Log Analytics Workspaces and click on Create.Ĭreate your Log Analytics workspace - you can use a single workspace for multiple data sources, or one per source. The first step here is to create a Log Analytics Workspace. You will need to have Azure AD P1 or P2 licensing in order to redirect the Azure AD logs, and an Azure subscription to create the workspace. In this post I am going to demonstrate redirecting Azure AD logs to Log Analytics, and then build a dashboard showing various data from those logs. Log Analytics is part of Azure and is a great solution for analysing and interrogating logs across a huge assortment of Azure services. By Katy Nicholson, posted on 14 February, 2022 ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |