Don't worry. Not everyone knows it...

I t’s been a while since I started working on data analysis part. When it comes to data analysis, it’s all about how efficiently one can filter and fetch the small set of useful data from humongous collection. I used Kusto Query Language (KQL) for writing advanced queries for Azure Log Analytics. At first, when you will start writing queries, it would be very daunting and keeping that in mind, I thought, I should share a few of those queries which could save huge on the beginner’s time. Hence, my next few posts would be mostly based on how to achieve expected output using KQL . So, let’s get started with a simple scenario first. Below is the sample data on which we are going to query: GenerationDate IngestionTime DescriptionTitle DescriptionDetail FeedKey 2020-05-21 00:00:00:0000000 2020-05-25 02:00:00:0000000 Schedule Task Read feed from server 1 acbf-uhef-4t5i-dfff 2020-0

Recently I received a request from one of my readers on how to tailor Office deployments and to be specific, how to exclude Teams from deployment configuration file. Let’s navigate to https://config.office.com/ from the browser. This is the place from where administrators can manage and deploy office products and subscriptions. You can see that there are two options on the page:  Create a new configuration  Import your configuration Here I am going to create a new configuration, but if you have existing configuration, you can import that too and update it based on your business needs. Once you have entered the Deployment Settings page, there are many options which need to be configured. Architecture Selection Select the architecture for which we are creating a deployment: Office Suite Selection Next is to select the Office Suite: Version Selection Next is to select the version which we want to deploy:

You may have come across a requirement, wherein you needed to update  Azure DevOps  objects programmatically and it is obvious that there must be some  authentication  mechanism which has to be in place. Now, there are many methods one can use to authenticate, but for this post, I’ve specifically chosen personal access token.  PAT , which is short for  Personal Access Token  is a way to provide an alternate password to authenticate to  Azure DevOps . To understand more about how to generate this token and how to utilize this, let’s follow certain steps and make a successful REST API call. You can checkout more about it on my article at Csharpcorner website.

Today, I've something good to share. Recently I was given an opportunity to talk in one of the technical conference named https://www.2020twenty.net/lightup/ , which was a fund raising event to support UNICEF in order to take a stand against COVID19 and it was organized by C# Corner and The Tech Platform.  I spoke on a topic ' Azure Bot Services Utilizing LUIS Capabilities ' which was a very wonderful experience. Hope recording of the same will be available soon.

Sometimes when we need to call APIs, we are just given the information about the entities in the form of OData metadata . Now when we are not aware about possible methods and their parameters which are exposed for use, it becomes very cumbersome and time consuming to call even a single method. Till some extent, we can still manage our life for Get methods as they are easy to guess using entity names, but when it comes to PUT/POST/PATCH , things are not straight forward. And here comes the need to generate classes with given metadata. Let’s have a look, on how we can generate these client-side proxy classes. Install the required Visual Studio Extension I’m using Visual Studio 2019 but the equivalent features are available in other versions too. Navigate to Manage Extensions dialog and search for OData Connected Service as shown below and install it. Using this tool, one can easily generate classes for all the entities and complex types which are menti