--- title: "Setting Up Azure Log Analytics Integration" slug: "setting-up-azure-log-analytics-for-integration-with-decisions" updated: 2026-04-07T20:15:01Z published: 2026-04-07T20:15:01Z --- > ## Documentation Index > Fetch the complete documentation index at: https://documentation.decisions.com/llms.txt > Use this file to discover all available pages before exploring further. # Setting Up Azure Log Analytics Integration ## Breaking Changes **The Azure Monitor HTTP Data Collector API will be deprecated on September 14th, 2026. Affected Areas: Legacy (9.22 and below), Azure Log Analytics will no longer work upon upgrade to 9.23.** ## Overview Users with v9 installations can integrate with **Azure Log Analytics** for external logging capabilities, storage, and organizing logs for [**Azure C****ontainerization**](https://documentation.decisions.com/docs/deploying-containers-on-azure-1). Azure Log Analytics allows Azure users to run queries on information gathered via the **Azure****Monitor**tool. These tools can be used to log and monitor **Decisions Studio** from outside the environment. Logging can be accomplished via [Environment Variables](/v9/docs/setting-up-azure-log-analytics-for-integration-with-decisions#environment-variables-method)****or****[Logging Settings](/v9/docs/setting-up-azure-log-analytics-for-integration-with-decisions#logging-settings-method). ### Prerequisites - An active [Azure](https://azure.microsoft.com/en-us/)account with an established [Resource Group](https://docs.microsoft.com/en-us/azure/azure-monitor/insights/resource-group-insights). - A v9 Decisions environment. - [Installation](https://documentation.decisions.com/v9/docs/installing-modules-decisions) of the AzureServices Module. ### Considerations Users must ensure the proper prerequisites are met in the Azure workspace according to individual/company requirements to minimize issues during configuration. --- ## Configuration 1. Log in to [**Azure Portal**](https://portal.azure.com/). ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2022-01-10_10h00_29.png) 2. From the Azure Portal, under **Azure****Services**, select **Create****a****resource**. ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2022-01-10_10h08_47.png) 3. In the **Search services and marketplace**box, search for and locate **Log****Analytics****Workspace**, then click **Create > Log Analytics Workspace**. ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2022-01-10_10h12_03.png) 4. From the **Create****Log****Analytics****workspace**, under **Project****details**, select the desired **Resource****group**. Then, under **Instance****details**, provide a **Name**, and select the same **Region**as the Resource Group. 5. Click **Review + Create**.![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2022-01-10_10h36_27.png) 6. Navigate to: - **Monitor > Data Collec****tion Rules > Select DCR > Overview**, and copy the **Immutable ID**.![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2026-04-06_13h19_07(1).png) - **Microsoft Entra ID > Overview**, and copy the **Tenant ID**.![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2026-04-06_13h34_30.png) - **Microsoft Entra ID > App registrations**, and copy the **Client ID**.![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2026-04-06_13h35_34.png) - The **Client Secret** can be copied during **App Registration**. ### Environment Variables Method 1. From the Local File System****of the Decisions v.9 installation, press the Windows key, or select the **Search**icon on the bottom toolbar, then locate and open the **Edit****system****environment****variables****Control****Panel**.![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2022-01-10_10h49_52.png) 2. From the **System****Properties**window, click the **Environment****Variables...** button. ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2022-01-10_10h53_48.png) 3. From the **Environment****Variables**window, under **System****Variables**, click **New...** 4. In the resulting New System Variable window, in the Variable name box, add the following Variable names, and paste the previously copied workspace ID in the Variable value box. Then, click Ok. - **DECISIONS_AZURE_LOG_INGESTIONENDPOINT** = Logs Ingestion URL for data collection endpoint. - **DECISIONS_AZURE_LOG_IMMUTABLEID** = ImmutableId for Data Collection Rules (DCR). - **DECISIONS_AZURE_LOG_STREAMNAME** = Output stream name of target (Log Analytics API, can be accessed from DCR) - **DECISIONS_AZURE_LOG_TENANTID** = Directory (tenant) ID of registered application (Microsoft Entra ID) - **DECISIONS_AZURE_LOG_CLIENTID** = Application (client) ID of Microsoft Entra application. - **DECISIONS_AZURE_LOG_CLIENTSECRET** = Client secret for registered Entra Application - **DECISIONS_AZURE_LOG_BUFFERSIZE** = Buffer for the logs to be stored in before they are successfully sent or batched. - **DECISIONS_AZURE_LOG_BATCHSIZE**= Number of log records sent in a request. - If desired, provide the Variable "DECISIONS_LOG_SERILOG_DEBUG" with the Value "True". Serilog.txt is a file that records any errors that occur with Azure Logging. By adding "DECISIONS_LOG_SERILOG_DEBUG" to the Local File System's list of environment variables and setting it to "true", it will create the file within the /Logs directory.![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2026-04-06_14h06_40.png) 5. From the Environment Variables window, click OK. Then, click OK from the System Properties window to save and close the window. ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2026-04-06_14h15_29.png) 6. After specifying the above variables, Users must restart the Decisions service for the variables to be applied and for the log sink to be created properly. Upon startup, environment variables that were configured in **Logging Settings > Azure Log Settings** should be displayed. 7. Proceed to [Running Logs](/v9/docs/setting-up-azure-log-analytics-for-integration-with-decisions#running-logs). ### Logging Settings Method Note for Azure Log Analytics Settings No additional action is required for Azure Log Analytics settings.  1. Navigate to **System > Settings > Logging Settings**, then open **Azure Log Analytics**. ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2024-08-08_09h12_36.png) 2. From the **Azure Log Analytics** window, select the desired **Levels**. Then, under SETTINGS, enter the following values: - Endpoint - Immutable ID - Stream Name - Tenant ID - Client ID - Client Secret - Buffer Size - Users must restart the decisions service after selecting **Is Enabled** for the setting to take effect. - After entering the required fields, click OK.![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2026-04-07_11h03_05.png) ### Running Logs 1. [**Restart**](https://documentation.decisions.com/v9/docs/restart-decisions-application)the Decisions service to ensure that Decisions knows the **Azure****Log**settings.![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2022-01-10_11h24_17.png) 2. Navigate back to the Portal for the Log Analytics workspace; under the **General**category on the left-hand side of the screen, select **Logs**. 3. Close out of the Queries window and create a New Query in the Query Editor, input the Log Name (The one defined in the environment variable **DECISIONS_AZURE_LOG_STREAMNAME**), then click Run.![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2026-04-06_14h35_34.png) 4. Verify the expected Logs display as expected. Filtering Logs If desired, the resulting Logs may be filtered using [**Kusto Query Language (KQL)**](https://docs.microsoft.com/en-us/azure/data-explorer/kusto/query/). ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2026-04-06_14h37_16.png) --- ## Feature Changes | Description | Version | Date | Developer Task | | --- | --- | --- | --- | | The Azure Monitor HTTP Data Collector API will be deprecated on September 14th, 2026. | 9.23 | April 2026 | [DT-046947] | For further information on Modules, visit the [Decisions Forum](https://community.decisions.com/categories/Modules).