Check the health of your exported Azure Sentinel logs in your ADX cluster

Check the health of your exported Azure Sentinel logs in your ADX cluster

This article is contributed. See the original author and article here.

More and more Azure Sentinel customers are opting for long-term retention of their logs in Azure Data Explorer (ADX), either due to compliance regulations, or because they still want to be able to perform investigations on their archived logs in the event of a security incident.


As the Azure Sentinel ingestion price includes 90 days of retention for free, the option of keeping the logs for longer periods in Azure Data Explorer is preferred by many (see Using Azure Data Explorer for long term retention of Azure Sentinel logs – Microsoft Tech Community). 


 


Even though the Azure Sentinel + ADX solution requires little to no maintenance, we wanted to provide a solution for our customers to keep an eye on the number of events and overall status of their ADX clusters and databases. For this reason, we have created two tools: the ADXvsLA workbook and the ADX Health Playbook. The workbook will allow you to have a look at the number of logs on Azure Sentinel & ADX and the overall health of your ADX cluster. The playbook will send you a warning if an unexpected delay in the ingestion of ADX is detected.


 


 


Below, we will describe both in more detail:


 


ADXvsLA Workbook


 


When you open the workbook, you can select the following parameters:



  • the ADX cluster and database

  • the Azure Sentinel workspace from which the logs are exported to the aforementioned ADX cluster,

  • as well as the time range for which you want to see data


Use the Show Help toggle to see a detailed explanation of each section.


 


1.png


 


Raw Tables


When you ingest logs from Azure Sentinel to ADX, the logs are first ingested into an intermediate table with raw data. This raw data is updated by a function with an update policy and is saved to its destination table with the correct mapping. Afterwards, the data is deleted, which is why you will typically see that these raw tables are empty. The retention policy should also be set for 0 days.


 


2.png


 


Final ADX Tables


In this section, you will see information about the final ADX tables, which have the right schema and can be queried from Azure Sentinel. You will find information regarding the row count, size, retention policy and hot cache size etc.


4.png


 


Select one of the table names to generate the comparison section. This is where you can see the differences between the table on ADX and on your Log Analytics workspace. Then, select the time range for which you want to see the comparison.


In the table you will find:



  • The number of entries in ADX, in Log Analytics, and the difference in number of logs between them.

  • How long it has been since the last log was received

  • The timestamp of the last logs.

  • The number of new logs received in Log Analytics since the last log in ADX was received


3.png


 


Notice the New in Log Analytics column





    • In the screenshot, you can see there are 52 logs in the “New in Log Analytics” column. This means that, at the time we compared the tables, there were 52 entries that had not reached ADX yet.
      If this happens, you should compare the timestamp and the difference for the last log that was received. In this case, it is around 15 minutes. Delays of 30 minutes or less are expected, so this means your tables are working as expected.

    • It is also possible that you see a negative number in the New in Log Analytics column. This could happen if, due to the lag in ADX, there were Log Analytics logs from the previous period that were received in ADX during the current period. Let’s suppose that you ingested 1000 logs in Log Analytics on the previous 24h window, but only 990 reached ADX in that period; and then you ingested 1000 logs again on the current 24h window, and all those logs, plus the 10 logs from the previous day, reached ADX. In this case, you will see that the “New in Log Analytics” column would say -10. In these cases, you only need to look at the LastTM difference. If it is around 30 minutes or less, then it will be fine.


     




Finally, at the bottom of the workbook you will see metrics regarding events received, events dropped, received data, volume and other metrics.


 


ADX Health Playbook


 


The ADX Health Playbook compares the number of logs in your Azure Sentinel tables and ADX tables periodically (every 24h by default) and sends you a warning via email if it detects a difference in the number of logs that may require your attention (that is, in the “New in Log Analytics” column mentioned previously). As it takes logs a few minutes to reach ADX after having been ingested into Log Analytics, the query in the playbook by default looks back at the period between the last 25h and last 30min.


Please read the accompanying readme.md file on GitHub to set it up.


 


We hope you find these tools useful! If you have any suggestions for improving this content or any questions, please leave us a comment.

Meet a recent Microsoft Learn Student Ambassador graduate: Haimantika Mitra

Meet a recent Microsoft Learn Student Ambassador graduate: Haimantika Mitra

This article is contributed. See the original author and article here.

 


Welcome to the next installment in our blog series highlighting Microsoft Learn Student Ambassadors who achieved the highest milestone of Gold and have recently graduated from university.  Each blog features a different student and highlights their accomplishments, their experience in the Student Ambassadors community, and what they’re up to now.


 


Today we’d like to introduce Haimantika Mitra who is from India and graduated recently from the Siliguri Institute of Technology.


 


Student_Developer_Team_1-1629837661823.png


 


Responses have been edited for clarity and length. 


 


When you joined the Microsoft Learn Student Ambassadors community in January 2020, did you have specific goals you wanted to reach, and did you achieve them? How has the program helped to prepare you for the next chapter in your life?



Since joining, my life has taken a different turn, a good turn!


 


When I first joined the community, I had very little to no idea about community building or about tech. In general, I was a person with an ambition–I was always up for learning, but I had no idea where to start. The Student Ambassadors community has helped me face imposter syndrome [editor’s note: this is the belief that you are not as capable as others perceive you to be].  The community has helped me learn tech skills that bagged me my first internship, build a social brand for myself, and make some good friends for life.


 


In my initial days, I used to attend a lot of events organized by my fellow Student Ambassadors and the community. I was introduced to new tech industry leaders who inspired me to learn and grow. I can clearly recall when I attended an event in April 2020 on Power Apps by Microsoft’s Dona Sarkar.  She gave us a small assignment to go through a Microsoft Learn module. Being totally awed by her and the technology, I immediately completed it, starting my journey of learning Microsoft Power Platform. After that day, I never looked back–I kept learning and sharing. I was conducting events and hackathons and interacting with a lot of inspiring people. To date, I continue to learn and deliver, but this community has given me everything I ever dreamed of.


 


In the Student Ambassadors community, what was the top accomplishment that you’re the proudest of and why?


 


It is a bit difficult to choose one event, because I had so many great ones that I am proud of! But being a speaker at Microsoft Build 2020 is something that I am very ecstatic about. I never imagined being a part of a global event–it was my first and thus very special. From speaking in front of a mirror to addressing such a huge audience, I am proud of who I have become. This event helped me gain the confidence I was lacking for so long. It introduced me to some amazing personalities, and helped me get involved in the community more.


 


I’ve spoken at various other Microsoft events and built solutions for people, specifically for the black, Asian, and minority ethnic (BAME) communities, I’ve been a part of the Black Minds Matter hackathon and have helped women in my country and the EMEA region upskill on Power Platform.


 


I posted about what I am learning every day, and as a result, in my final year of university, I was approached by various companies to work on their Power Platform teams. The opportunities I received from the Student Ambassador program gave me the necessary push. Everything else followed, and it was magical!


 


What do you have planned for after graduation?  What’s next for you?


 


I will continue with community work. I consider myself a product of the community, and I know there are many like me who are looking for a direction. I wish to be that person who can provide them with direction.  I will also be joining Microsoft in a full-time capacity as a support engineer. It is a dream to me;  all the learnings that I had from the community helped me get closer to it.


 


If you were to describe the community to a student who is interested in joining, what would you say about it to convince him or her to join?


 


Most students have a common question: “How do I get started in tech?” I would simply say to them that if they are looking for the answer, this is the right place to be! I shall also brief them on the amazing perks such as the 1:1 mentoring sessions we have, Microsoft Training Certification vouchers, access to LinkedIn learning, tech-specific leagues headed by Microsoft developer advocates, the fun we have in the community calls, and more.


 


What advice would you give to new Student Ambassadors?


 


Embrace the opportunity that they are receiving. Initially attend as many sessions as possible, use Microsoft Learn (the best place to upskill from), make use of all the opportunities that Ambassadors are given, and check Teams {editor’s note: this is the communication platform Ambassadors and program managers use to communicate and collaborate] for 10 minutes a day to make sure that you do not miss on any notifications or opportunities.


 


What is your motto in life, your guiding principle?


 


“Technology for everyone”.  I am trying my best to bring more people to tech rather than having them be scared of it. I look forward to taking this goal bigger and helping as many as I can.


 


What is one random fact about you that few people know about?


 


People have seen the side of me that hustles, that works hard a lot, but what they do not know is, I am a “serial chiller”.  There are times when I pull all-nighters binge watching TV or just lying down and doing nothing.


 


We wish you the best of luck in all your future endeavors, Haimantika!

Analyzing FHIR data with Azure Synapse Analytics

Analyzing FHIR data with Azure Synapse Analytics

This article is contributed. See the original author and article here.

This blog has been authored by Ranvijay Kumar, Principal Program Manager, Microsoft Health & Life Sciences


 


HL7 Fast Healthcare Interoperability Resources (FHIR®) is quickly becoming the de facto standard for persisting and exchanging healthcare data. FHIR specifies a high-fidelity and extensible information model for capturing details of healthcare entities and events.


This article will teach you a simple approach to creating analytical data marts by exporting, transforming, and copying data from Azure API for FHIR to Azure Synapse Analytics, which is a limitless analytics service designed for data warehousing and big data workloads. You can complete your Business Intelligence (to Artificial Intelligence (AI) analytics with Synapse due to the deep integration with Power BI, Azure Machine Learning, and Azure Cognitive services.


 


 


 


FHIR to Synapse.png


 


 


In this approach, as illustrated in the diagram, you will use the $export operation in Azure API for FHIR to export FHIR resources in NDJSON format (newline delimited JSON) to Azure storage. You will then use T-SQL from any of the serverless or the dedicated SQL pools in Synapse to query against those NDJSON files and optionally save the results into tables for further analysis.


 


 


Exporting FHIR data to Azure storage


 


Azure API for FHIR implements the $export operation defined by the FHIR spec to export all – or a filtered subset – of FHIR data in NDJSON format. It also supports de-identified export to enable secondary use of healthcare data. You can configure the server to export the data to any kind of Azure Storage account; however, we recommend exporting to ADLS Gen 2 for best alignment with Synapse.


Let’s consider a scenario in which data scientists want to analyze clinical data of patients who are former smokers. For the study, data scientists need an initial copy of data from the FHIR server followed by incremental data for the same set of patients every month for the next two years.


 


 


The first step to get this data is to identify the patients in the FHIR server who are former smokers. The following GET call searches the FHIR server using the LOINC code 72166-2 (Tobacco smoking status) for Observation, and SNOMED code 8517006 (Former smoker) for Observation value-concept to get subjects of the observations who are former smokers. You may need to use different codes depending on how your data is coded.


 


 









 


https://{{fhirserverurl}}/Observation?code=72166-2&value-concept=8517006&_elements=subject


 



 


 


You need to save this list of patients to enable exporting their clinical data monthly. There are a few options to manage a collection of resources in FHIR. Since Group is supported by the $export operation, you will manage the collection of patient resource IDs as a Group. Use the results from the above search query to create a person-type Group.


 


 









 


{


    “resourceType”: “Group”, “id”: “1”,”type”: “person”, “actual”: true,


    “member”: [{“entity”: {“reference”: “Patient/44f6f10e-96c2-4802-b857-4861f1802522”}},


                        … other patient entities from the result …


              ]


}


 



 


 


Once you have a Group, you can export all the data related to the patients in the Group with the following async REST call:


 Note: Azure API for FHIR takes an optional container name to simplify the organization of exported data.


 


 









 


https://{{fhirserverurl}}/Group/{{GroupId}}/$export?_container={{BlobContainer}}


 



 


 


You can also use _type and _typefilter parameters in the $export call to restrict the resources we you want to export.  Finally, you can use _since parameter in the $export call to do incremental exports every month for two years to meet your original requirement. This parameter restricts export to the resources that have been created or updated since the supplied time.


 


 









 


https://{{fhirserverurl}}/Group/{{GroupId}}/$export?_container={{BlobContainer}}&_since=2021-02-06T01:09:53.526+00:00


 



 


 


Now that you have data in ADLS Gen 2, let’s talk about Synapse and see how you can load it to Synapse.


 


 


About Azure Synapse Analytics


 


Create a pipeline


You can use a variety of REST clients such as Postman to export the data from the FHIR server and use Synapse Studio or any other SQL client to run the above T-SQL statements. However, it is a good idea to convert these steps into a robust data movement pipeline using Synapse Pipelines. You can use the Synapse Web activity for triggering the export, and the Stored procedure activity to run the T-SQL statements in the pipeline.


 


Conclusion


You can use the FHIR $export API and T-SQL to transform and move all or a filtered subset of data from FHIR server to Synapse Analytics. After the initial data load, the _since parameter in the $export operation can be used to do incremental data load. An ETL pipeline with the steps mentioned in this article can be used to keep the data in the FHIR server and the Synapse Analytics in sync.


 


 


®FHIR is registered trademark of Health Level Seven International, registered in the U.S. Trademark Office and is used with their permission.

OneDrive usage reports return GUIDs or pseudonymized values instead of actual data values.

This article is contributed. See the original author and article here.

OneDrive usage reports and Graph API endpoints /reports/getOneDriveUsageAccountDetail started returning GUIDs for ownerDisplayName, ownerPrincipalName, and siteURL instead of the actual data values that had previously been returned.


 


The removal of user-identifiable information in Admin Center reports was announced via the following Message Center post MC275344 .


This is an expected behavior, which was implemented starting Sep 1st, 2021. Please see article https://docs.microsoft.com/en-US/microsoft-365/admin/activity-reports/activity-reports?WT.mc_id=365AdminCSH_inproduct&view=o365-worldwide.


 


Note: The article needs to be updated, with right settings to change.


 


To revert to default you will need to take following steps:


 


Global administrators can revert this change for their tenant and show identifiable user information if their organization’s privacy practices allow it. It can be achieved in the Microsoft 365 admin center by following these steps:


 


In the admin center, go to the Settings > Org Settings > Services page.


 


Select Reports.


 


Uncheck “In all reports, display de-identified names for users, groups, and sites.”


 


It’ll take a few minutes for these changes to take effect on the reports in the report’s dashboard. This setting also applies to the reports API. Showing identifiable user information is a logged event in the Microsoft 365 compliance center audit log.

Commercial previews for Windows 11 and Windows 10, version 21H2

Commercial previews for Windows 11 and Windows 10, version 21H2

This article is contributed. See the original author and article here.

Commercial organizations can now explore and validate Windows 11 and Windows 10, version 21H2 that will be released later this year.


Today, we released Windows 11 and the Windows 10, version 21H2 feature update for commercial preview. Organizations enrolled in the Windows Insider Program for Business can access these builds through all standard channels, including Windows Update, Windows Server Update Services (WSUS), Azure Marketplace, and the Windows Insider Program ISO download page. Along with commercial pre-release availability, we are also offering free support for commercial organizations running these builds. This means you can test these releases—and your preferred deployment methods—while remaining supported prior to general availability.


Access commercial previews using Windows Update or Windows Update for Business


Commercial devices configured for the Windows Insider Program Release Preview Channel via the Windows Update Settings page or via Windows Update for Business policy will automatically be offered Windows 11 as an optional upgrade provided that the device(s) meet the hardware requirements and have taken the September 1, 2021 optional cumulative update (KB5005101). If you do not wish to upgrade a device to Windows 11, simply select “Stay on Windows 10 for now”, at which point Windows 10, version 21H2 will be offered instead. Commercial devices in the Release Preview Channel that do not meet the hardware requirements necessary to support Windows 11 will be offered Windows 10, version 21H2 automatically instead.


Both previews are completely optional. You can choose to remain on your current version of Windows and continue to receive preview builds of quality updates for that version.


 


The Windows Update interface showing that upgrade to Windows 11 is ready and free.The Windows Update interface showing that upgrade to Windows 11 is ready and free.


 


The Windows Update view in Settings, showing as up to dateThe Windows Update view in Settings, showing as up to date


If you are using MEM Intune, simply set “Servicing channel” to “Windows Insider – Release Preview”:


 


Setting Servicing channel to Windows Insider - Release PreviewSetting Servicing channel to Windows Insider – Release Preview


 









Note: We consider a device a commercial device if: a) it is not running Windows 10 Home edition; b) it is being managed by an IT administrator (whether via Microsoft Endpoint Manager or other endpoint management solution); or c) it has a volume license key or commercial ID, or is joined to a domain.



Access commercial previews using Windows Server Update Service (WSUS)


Both Windows 11 and Windows 10, version 21H2 are now available in the “Windows Insider Pre-release” category in WSUS and Microsoft Endpoint Manager (MEM) Configuration Manager. If you do not see them offered, simply sync the category and you will see them.


 


Windows 11 and Windows 10, version 21H2 are now availableWindows 11 and Windows 10, version 21H2 are now available


To access the Windows 11 preview build, devices must first take the September 1, 2021 optional cumulative update (KB 5005101). If a device is configured to send diagnostic data, but does not meet the hardware requirements, the Windows 11 upgrade will be marked as inapplicable in WSUS.


To access the Windows 10, version 21H2 preview build, devices running Windows 10, version 2004, version 20H2, or version 21H1 can leverage the enablement package path to update to version 21H2. Devices running versions prior to Windows 10, version 2004 will first need to do a full OS swap to receive Windows 10, version 21H2.


Access commercial previews from the Windows Insider Program ISO Download page


Simply go to the Windows Insider Program ISO Downloads site and select either the Windows 11 ISO (listed under Dev Channel and Beta Channel) or the Windows 10, version 21H2 ISO (listed under the Release Preview Channel).


 









Note: A clean installation will utilize your existing Windows 10 license keys or activate using Azure AD. No net new Windows 11 keys are required.



Access commercial previews through Azure Marketplace


On Azure Marketplace, we have added a new Windows 11 Preview offering with various images. For Windows 10, version 21H2, simply check out the Windows 10 Preview offering.


 


Windows 11 PreviewWindows 11 Preview


Supporting your preview experience


Regardless of how you choose to deploy the release previews of either Windows 11 or Windows 10, version 21H2, we will keep you supported! If you encounter an issue, please report it to feedback hub or reach out to us directly through our free support offering for commercial organizations.


Microsoft is committed to ensuring your applications work on the latest versions of our software. Windows 11 has been built with compatibility in mind. Our promise states that apps that worked on Windows 7, 8.1, and 10 will work on Windows 11. If you experience a compatibility issue when deploying Windows 11 or Windows 10, version 21H2, you can utilize App Assure with Microsoft FastTrack to help remediate your application issues. App Assure will help troubleshoot the issue, determine the root cause, and fix the application. It is available at no additional cost for eligible customers with 150+ seats.


With that, we encourage you to go explore these releases, and don’t forget to reach out to me, @ariaupdated, on Twitter or message me on Tech Community with any feedback on how we can improve the Windows Insider Program for Business and our pre-release commercial offerings!