Problem You need to know the maximum amount of time that the SQL Insights data can be stored in Azure Log Analytics. Solution The maximum amount of time that SQL insights data can be stored in Azure Log Analytics is 730 days.  

In this post, you’ll learn more about the Error Bad Request (400) that is returned when working with the Azure Table Storage Azure Storage Error HTTP Status Code HostInformationNotPresent Bad Request (400) Azure Table Storage Error Description The required host information is not present in the request. You must send a non-empty Host header or include the absolute URI in the request line.

Problem You are designing an Azure resource deployment that will use Azure Resource Manager templates. The deployment will need to use Azure Key Vault to store secrets. You will need to recommend a solution that prevents the IT staff to perform the deployment from retrieving the secrets directly from the Key Vault. How would you do this? Solution You will need to set enabledForTemplateDeployment in…

In this post, you’ll learn more about the Error Bad Request (400) that is returned when working with the Azure Table Storage Azure Storage Error HTTP Status Code EntityTooLarge Bad Request (400) Azure Table Storage Error Description The entity is larger than the maximum size permitted.

Problem Statement Assume that you have a Azure App Service Web App with Azure Blob storage and Azure SQL database and you are using Application Insights integrated as well. You will need to use the monitoring services for various functionalities with-in your application. Solution There are quite a few monitoring services that you can use with-in your azure subscription. You can use the below services….

In this post, you’ll learn more about the Error Conflict (409) that is returned when working with the Azure Table Storage Azure Storage Error HTTP Status Code TableBeingDeleted Conflict (409) Azure Table Storage Error Description The specified table is being deleted.

In this post, you’ll learn more about the Error Bad Request (400) that is returned when working with the Azure Table Storage Azure Storage Error HTTP Status Code TooManyProperties Bad Request (400) Azure Table Storage Error Description The entity contains more properties than allowed.

In this post, you’ll learn more about the Error Bad Request (400) that is returned when working with the Azure Table Storage Azure Storage Error HTTP Status Code PropertiesNeedValue Bad Request (400) Azure Table Storage Error Description Values have not been specified for all properties in the entity.

In this post, you’ll learn more about the Error Bad Request (400) that is returned when working with the Azure Table Storage Azure Storage Error HTTP Status Code DuplicatePropertiesSpecified Bad Request (400) Azure Table Storage Error Description A property is specified more than one time.

In this post, you’ll learn more about the Error Bad Request (400) that is returned when working with the Azure Table Storage Azure Storage Error HTTP Status Code InvalidInput Bad Request (400) Azure Table Storage Error Description If-Match or If-None-Match headers cannot be specified if the target type does not have etag properties defined.

In this post, you’ll learn more about the Error Bad Request (400) that is returned when working with the Azure Table Storage Azure Storage Error HTTP Status Code PropertyValueTooLarge Bad Request (400) Azure Table Storage Error Description The property value is larger than the maximum size permitted.

In this post, you’ll learn more about the Error Not Found (404) that is returned when working with the Azure Table Storage Azure Storage Error HTTP Status Code EntityNotFound Not Found (404) Azure Table Storage Error Description The specified entity does not exist.

Problem Assume that you have an on-premise Hyper-V cluster that contains X number of virtual machines and the hosts are licensed under Microsoft Enterprise Agreement with Software Assurance. You are planning to replace the on-premise virtual machines with the Azure Virtual Machines. You need to minimize the compute costs of Azure virtual machines. Solution Enabling the Azure Hybrid Benefit for Azure Virtual Machines will allow…

In this post, you’ll learn more about the Error Bad Request (400) that is returned when working with the Azure Table Storage Azure Storage Error HTTP Status Code XMethodNotUsingPost Bad Request (400) Azure Table Storage Error Description The request uses X-HTTP-Method with an HTTP verb other than POST.

Problem Assume that you have an Azure subscription that contains 300 Azure Virtual Machines that runs on Windows Server 2016. You will need to centrally monitor all warning events in the System logs of Virtual machines. Solution Simply create a new resource of type “Log Analytics Workspace” in Azure and then install the Microsoft Monitoring Agent in the Virtual Machines.

In this post, you’ll learn more about the Error Unsupported Media Type (415) that is returned when working with the Azure Table Storage Azure Storage Error HTTP Status Code JsonFormatNotSupported Unsupported Media Type (415) Azure Table Storage Error Description JSON format is not supported.

In this post, you’ll learn more about the Error Bad Request (400) that is returned when working with the Azure Table Storage Azure Storage Error HTTP Status Code PropertyNameInvalid Bad Request (400) Azure Table Storage Error Description The property name is invalid.

Problem Assume that you have a ASP.NET Web API application and you see lot of visitors reporting issues with the application. You will need to identify issues by implementing Live Monitoring and setup smart alerting to detect anomalies in the data. Solution You can use Application Insights. Application Insights is part of Azure Monitor is an Application Performance Management (APM) service for developers which can…

In this post, you’ll learn more about the Error Bad Request (400) that is returned when working with the Azure Table Storage Azure Storage Error HTTP Status Code InvalidInput Bad Request (400) Azure Table Storage Error Description If-None-Match HTTP header cannot be specified for PUT operations.