---
title: "setup Azure ChatGPT()"
slug: "ai-azure-chat-gpt-setup"
updated: 2026-08-10T06:06:18Z
published: 2026-08-10T06:06:18Z
canonical: "docs.lobstersoftware.com/ai-azure-chat-gpt-setup"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lobstersoftware.com/llms.txt
> Use this file to discover all available pages before exploring further.

# setup Azure ChatGPT()

This function allows you to establish an Azure OpenAI Service ChatGPT API Session.

Several individual sessions can be established, each session having its own prompt and chat history. After the end of Phase 3, all sessions are removed.

## Parameters

| Parameter | Description |
| --- | --- |
| a | (optional) Freely assignable session key. If nothing is specified here, a fixed internal session key is used. With individual session keys, multiple instances of ChatGPT sessions can be built up, where each instance has its own prompt and chat history. After the end of Phase 3, all instances are removed (also the internal one). |
| b | "true", if the session is to be established via a DMZ server (if available). Default: "false". |
| c | Your API URL. **Example:** "https://<your-resource-name>.openai.azure.com/openai/deployments/<deployment-id>/chat/completions". <your-resource-name> - The name of your Azure OpenAI Resource. <deployment-id> - The deployment name you chose when you deployed the model. |
| d | (optional) The API version. **Example:** "2023-03-15-preview". |
| e | Your API key. |
| f | The sampling temperature. Higher values will make the output more random/creative, while lower values will make it more focused and deterministic. Allowed values: "0.1" to "1". |
| g | The maximum number of tokens to generate in the chat completion. Allowed values: "1" to "4096". |
| h | (optional) Content for the role "system". **Example:** You are a database SQL expert and answer questions related to SQL statements. |

Mapping: Rules transfer the data from the source structure to the target structure. This is the core of the profile.

An optional security layer between the internet and the Integration Server. The DMZ receives incoming traffic, forwards it in a controlled manner, and protects the internal system from direct external access. When the Integration Server restarts, it buffers incoming requests.