This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Important
Items marked (preview) in this article are currently in public preview. This preview is provided without a service-level agreement, and we don't recommend it for production workloads. Certain features might not be supported or might have constrained capabilities. For more information, see Supplemental Terms of Use for Microsoft Azure Previews.
In this article, you learn how to use Azure AI Foundry to deploy AI21's Jamba family models as a serverless API with pay-as-you-go billing.
The Jamba family models are AI21's production-grade Mamba-based large language model (LLM) which leverages AI21's hybrid Mamba-Transformer architecture. It's an instruction-tuned version of AI21's hybrid structured state space model (SSM) transformer Jamba model. The Jamba family models are built for reliable commercial use with respect to quality and performance.
See our announcements of AI21's Jamba family models available now on Azure AI Model Catalog through AI21's blog and Microsoft Tech Community Blog.
Important
Models that are in preview are marked as preview on their model cards in the model catalog.
Certain models in the model catalog can be deployed as a serverless API with pay-as-you-go billing, providing a way to consume them as an API without hosting them on your subscription, while keeping the enterprise security and compliance organizations need. This deployment option doesn't require quota from your subscription.
The AI21-Jamba 1.5 Large model deployed as a serverless API with pay-as-you-go billing is offered by AI21 through Microsoft Azure Marketplace. AI21 can change or update the terms of use and pricing of this model.
To get started with Jamba 1.5 large deployed as a serverless API, explore our integrations with LangChain, LiteLLM, OpenAI and the Azure API.
An Azure subscription with a valid payment method. Free or trial Azure subscriptions won't work. If you don't have an Azure subscription, create a paid Azure account to begin.
An Azure AI Foundry project. The serverless API model deployment offering for Jamba family models is only available with projects created in specific regions. For a list of these regions, see Region availability for models in serverless API endpoints.
Azure role-based access controls (Azure RBAC) are used to grant access to operations in Azure AI Foundry portal. To perform the steps in this article, your user account must be assigned the owner or contributor role for the Azure subscription. Alternatively, your account can be assigned a custom role that has the following permissions:
On the Azure subscription—to subscribe the Azure AI Foundry project to the Azure Marketplace offering, once for each project, per offering:
Microsoft.MarketplaceOrdering/agreements/offers/plans/readMicrosoft.MarketplaceOrdering/agreements/offers/plans/sign/actionMicrosoft.MarketplaceOrdering/offerTypes/publishers/offers/plans/agreements/readMicrosoft.Marketplace/offerTypes/publishers/offers/plans/agreements/readMicrosoft.SaaS/register/actionOn the resource group—to create and use the SaaS resource:
Microsoft.SaaS/resources/readMicrosoft.SaaS/resources/writeOn the Azure AI Foundry project—to deploy endpoints (the Azure AI Developer role contains these permissions already):
Microsoft.MachineLearningServices/workspaces/marketplaceModelSubscriptions/*Microsoft.MachineLearningServices/workspaces/serverlessEndpoints/*For more information on permissions, see Role-based access control in Azure AI Foundry portal.
These steps demonstrate the deployment of AI21 Jamba 1.5 Large or AI21 Jamba 1.5 Mini models. To create a deployment:
Search for and select an AI21 model like AI21 Jamba 1.5 Large or AI21 Jamba 1.5 Mini to open its Details page.
Select Deploy to open a serverless API deployment window for the model.
Alternatively, you can initiate a deployment by starting from the Models + endpoints page in Azure AI Foundry portal.
AI21 Jamba 1.5 Large or AI21 Jamba 1.5 Mini to open the Model's Details page.Your current project is specified for the deployment. To successfully deploy the AI21-Jamba family models, your project must be in one of the regions listed in the Prerequisites section.
In the deployment wizard, select the link to Azure Marketplace Terms, to learn more about the terms of use.
Select the Pricing and terms tab to learn about pricing for the selected model.
Select the Subscribe and Deploy button. If this is your first time deploying the model in the project, you have to subscribe your project for the particular offering. This step requires that your account has the Azure subscription permissions and resource group permissions listed in the Prerequisites. Each project has its own subscription to the particular Azure Marketplace offering of the model, which allows you to control and monitor spending. Currently, you can have only one deployment for each model within a project.
Once you subscribe the project for the particular Azure Marketplace offering, subsequent deployments of the same offering in the same project don't require subscribing again. If this scenario applies to you, there's a Continue to deploy option to select.
Give the deployment a name. This name becomes part of the deployment API URL. This URL must be unique in each Azure region.
Select Deploy. Wait until the deployment is ready and you're redirected to the Deployments page.
Return to the Deployments page, select the deployment, and note the endpoint's Target URI and the Secret Key. For more information on using the APIs, see the Reference section.
You can always find the endpoint's details, URL, and access keys by navigating to your project's Management center from the left navigation pane. Then, select Models + endpoints.
To learn about billing for the AI21-Jamba family models deployed as a serverless API with pay-as-you-go token-based billing, see Cost and quota considerations for Jamba models deployed as a serverless API.
You can consume Jamba family models as follows:
From the left navigation pane of your project, select My assets > Models + endpoints.
Find and select the deployment you created.
Copy the Target URI and the Key value.
Make an API request.
For more information on using the APIs, see the reference section.
Jamba family models accept both of these APIs:
/chat/completions for multi-turn chat or single-turn question-answering. This API is supported because Jamba family models are fine-tuned for chat completion.The Azure AI model inference API schema can be found in the reference for Chat Completions article and an OpenAPI specification can be obtained from the endpoint itself.
Single-turn and multi-turn chat have the same request and response format, except that question answering (single-turn) involves only a single user message in the request, while multi-turn chat requires that you send the entire chat message history in each request.
In a multi-turn chat, the message thread has the following attributes:
user and assistant role messagesThe following pseudocode is an example of the message stack for the fourth call in a chat request that includes an initial system message.
[
{"role": "system", "message": "Some contextual information here"},
{"role": "user", "message": "User message 1"},
{"role": "assistant", "message": "System response 1"},
{"role": "user", "message": "User message 2"},
{"role": "assistant"; "message": "System response 2"},
{"role": "user", "message": "User message 3"},
{"role": "assistant", "message": "System response 3"},
{"role": "user", "message": "User message 4"}
]
Use the method POST to send the request to the /v1/chat/completions route:
Request
POST /v1/chat/completions HTTP/1.1
Host: <DEPLOYMENT_URI>
Authorization: Bearer <TOKEN>
Content-type: application/json
Payload is a JSON formatted string containing the following parameters:
| Key | Type | Required/Default | Allowed values | Description |
|---|---|---|---|---|
model |
string |
Y | Must be jamba-1.5-large or jamba-1.5-mini |
|
messages |
list[object] |
Y | A list of objects, one per message, from oldest to newest. The oldest message can be role system. All later messages must alternate between user and assistant roles. See the message object definition below. |
|
max_tokens |
integer |
N 4096 |
0 – 4096 | The maximum number of tokens to allow for each generated response message. Typically the best way to limit output length is by providing a length limit in the system prompt (for example, "limit your answers to three sentences") |
temperature |
float |
N 1 |
0.0 – 2.0 | How much variation to provide in each answer. Setting this value to 0 guarantees the same response to the same question every time. Setting a higher value encourages more variation. Modifies the distribution from which tokens are sampled. We recommend altering this or top_p, but not both. |
top_p |
float |
N 1 |
0 < value <=1.0 | Limit the pool of next tokens in each step to the top N percentile of possible tokens, where 1.0 means the pool of all possible tokens, and 0.01 means the pool of only the most likely next tokens. |
stop |
string OR list[string] |
N |
"" | String or list of strings containing the word(s) where the API should stop generating output. Newlines are allowed as "\n". The returned text won't contain the stop sequence. |
n |
integer |
N 1 |
1 – 16 | How many responses to generate for each prompt. With Azure AI Foundry's Playground, n=1 as we work on multi-response Playground. |
stream |
boolean |
N False |
True OR False |
Whether to enable streaming. If true, results are returned one token at a time. If set to true, n must be 1, which is automatically set. |
tools |
array[tool] |
N | "" | A list of tools the model may call. Currently, only functions are supported as a tool. Use this to provide a list of functions the model may generate JSON inputs for. A max of 128 functions are supported. |
response_format |
object |
N null |
"" | Setting to { "type": "json_object" } enables JSON mode, which guarantees the message the model generates is valid JSON. |
documents |
array[document] |
N | "" | A list of relevant documents the model can ground its responses on, if the user explicitly says so in the prompt. Essentially acts as an extension to the prompt, with the ability to add metadata. each document is a dictionary. |
The messages object has the following fields:
role: [string, required] The author or purpose of the message. One of the following values:
user: Input provided by the user. Any instructions given here that conflict with instructions given in the system prompt take precedence over the system prompt instructions.assistant: A response generated by the model.system: Initial instructions to provide general guidance on the tone and voice of the generated message. An initial system message is optional, but recommended to provide guidance on the tone of the chat. For example, "You are a helpful chatbot with a background in earth sciences and a charming French accent."content: [string, required] The content of the message.The tool object has the following fields:
type (required; str) - The type of the tool. Currently, only "function" is supported.function (required; object) - The function details.
name (required; str) - The name of the function to be called.description (optional; str) - A description of what the function does.parameters (optional; object) - The parameters the function accepts, described as a JSON Schema object.The document object has the following fields:
id (optional; str) - unique identifier. will be linked to in citations. up to 128 characters.content (required; str) - the content of the documentmetadata (optional; array of Metadata)
key (required; str) - type of metadata, like 'author', 'date', 'url', etc. Should be things the model understands.value (required; str) - value of the metadataSingle-turn example Jamba 1.5 large and Jamba 1.5 mini
{
"model":"jamba-1.5-large", <jamba-1.5-large|jamba-1.5-mini>
"messages":[
{
"role":"user",
"content":"I need help with your product. Can you please assist?"
}
],
"temperature":1,
"top_p":1,
"n":1,
"stop":"\n",
"stream":false
}
Single-turn example Jamba 1.5 large and Jamba 1.5 mini with documents
{
"model":"jamba-1.5-large", <jamba-1.5-large|jamba-1.5-mini>
"messages":[
{
"role":"system",
"content":'''<documents>
# Documents
You can use the following documents for reference:
## Document ID: 0
Text: Harry Potter is a series of seven fantasy novels written by British author J. K. Rowling.
## Document ID: 1
Text: The Great Gatsby is a novel by American writer F. Scott Fitzgerald.
</documents>'''},
{
"role":"user",
"content":"Who wrote Harry Potter?"
}
],
"temperature":0.4,
"top_p":1,
"n":1,
"stop":"\n",
"stream":false
}
Chat example (fourth request containing third user response)
{
"model": "jamba-1.5-large",
"messages": [
{"role": "system",
"content": "You are a helpful genie just released from a bottle. You start the conversation with 'Thank you for freeing me! I grant you one wish.'"},
{"role":"user",
"content":"I want a new car"},
{"role":"assistant",
"content":"🚗 Great choice, I can definitely help you with that! Before I grant your wish, can you tell me what kind of car you're looking for?"},
{"role":"user",
"content":"A corvette"},
{"role":"assistant",
"content":"Great choice! What color and year?"},
{"role":"user",
"content":"1963 black split window Corvette"}
],
"n":3
}
The response depends slightly on whether the result is streamed or not.
In a non-streamed result, all responses are delivered together in a single response, which also includes a usage property.
In a streamed result,
choices field.choices object structure is different.usage object.data object.data: [DONE].The response payload is a dictionary with the following fields.
| Key | Type | Description |
|---|---|---|
id |
string |
A unique identifier for the request. |
model |
string |
Name of the model used. |
choices |
list[object] |
The model-generated response text. For a non-streaming response it is a list with n items. For a streaming response, it is a single object containing a single token. See the object description below. |
usage |
object |
Usage statistics for the completion request. See below for details. |
The choices response object contains the model-generated response. The object has the following fields:
| Key | Type | Description |
|---|---|---|
index |
integer |
Zero-based index of the message in the list of messages. Might not correspond to the position in the list. For streamed messages this is always zero. |
message OR delta |
object |
The generated message (or token in a streaming response). Same object type as described in the request with two changes: - In a non-streaming response, this object is called message. - In a streaming response, it is called delta, and contains either message or role but never both. |
finish_reason |
string |
The reason the model stopped generating tokens: - stop: The model reached a natural stop point, or a provided stop sequence. - length: Max number of tokens have been reached. - content_filter: The generated response violated a responsible AI policy. - null: Streaming only. In a streaming response, all responses except the last will be null. |
The message response object contains the model-generated response. The object has the following fields:
| Key | Type | Description |
|---|---|---|
role |
string |
The role of the author of this message. |
content |
string or null |
The contents of the message. |
tool_calls |
array or null |
The tool calls generated by the model. |
The tool_calls response object contains the model-generated response. The object has the following fields:
| Key | Type | Description |
|---|---|---|
id |
string |
The ID of the tool call. |
type |
string |
The type of the tool. Currently, only function is supported. |
function |
object |
The function that the model called. |
The function response object contains the model-generated response. The object has the following fields:
| Key | Type | Description |
|---|---|---|
name |
string |
The name of the function to call. |
arguments |
string |
The arguments to call the function with, as generated by the model in JSON format. |
The usage response object contains the following fields.
| Key | Type | Value |
|---|---|---|
prompt_tokens |
integer |
Number of tokens in the prompt. Note that the prompt token count includes extra tokens added by the system to format the prompt list into a single string as required by the model. The number of extra tokens is typically proportional to the number of messages in the thread, and should be relatively small. |
completion_tokens |
integer |
Number of tokens generated in the completion. |
total_tokens |
integer |
Total tokens. |
{
"id":"cmpl-524c73beb8714d878e18c3b5abd09f2a",
"choices":[
{
"index":0,
"message":{
"role":"assistant",
"content":"The human nose can detect over 1 trillion different scents, making it one of the most sensitive smell organs in the animal kingdom."
},
"finishReason":"stop"
}
],
"created": 1717487036,
"usage":{
"promptTokens":116,
"completionTokens":30,
"totalTokens":146
}
}
data: {"id": "cmpl-8e8b2f6556f94714b0cd5cfe3eeb45fc", "choices": [{"index": 0, "delta": {"role": "assistant"}, "created": 1717487336, "finish_reason": null}]}
data: {"id": "cmpl-8e8b2f6556f94714b0cd5cfe3eeb45fc", "choices": [{"index": 0, "delta": {"content": ""}, "created": 1717487336, "finish_reason": null}]}
data: {"id": "cmpl-8e8b2f6556f94714b0cd5cfe3eeb45fc", "choices": [{"index": 0, "delta": {"content": " The"}, "created": 1717487336, "finish_reason": null}]}
data: {"id": "cmpl-8e8b2f6556f94714b0cd5cfe3eeb45fc", "choices": [{"index": 0, "delta": {"content": " first e"}, "created": 1717487336, "finish_reason": null}]}
data: {"id": "cmpl-8e8b2f6556f94714b0cd5cfe3eeb45fc", "choices": [{"index": 0, "delta": {"content": "mpe"}, "created": 1717487336, "finish_reason": null}]}
... 115 responses omitted for sanity ...
data: {"id": "cmpl-8e8b2f6556f94714b0cd5cfe3eeb45fc", "choices": [{"index": 0, "delta": {"content": "me"}, "created": 1717487336, "finish_reason": null}]}
data: {"id": "cmpl-8e8b2f6556f94714b0cd5cfe3eeb45fc", "choices": [{"index": 0, "delta": {"content": "."}, "created": 1717487336,"finish_reason": "stop"}], "usage": {"prompt_tokens": 107, "completion_tokens": 121, "total_tokens": 228}}
data: [DONE]
The Jamba family models are deployed as a serverless API and is offered by AI21 through Azure Marketplace and integrated with Azure AI Foundry for use. You can find Azure Marketplace pricing when deploying or fine-tuning models.
Each time a workspace subscribes to a given model offering from Azure Marketplace, a new resource is created to track the costs associated with its consumption. The same resource is used to track costs associated with inference and fine-tuning; however, multiple meters are available to track each scenario independently.
For more information on how to track costs, see Monitor costs for models offered through the Azure Marketplace.
Quota is managed per deployment. Each deployment has a rate limit of 200,000 tokens per minute and 1,000 API requests per minute. However, we currently limit one deployment per model per project. Contact Microsoft Azure Support if the current rate limits aren't sufficient for your scenarios.
Models deployed as a serverless API are protected by Azure AI content safety. With Azure AI content safety enabled, both the prompt and completion pass through an ensemble of classification models aimed at detecting and preventing the output of harmful content. The content filtering (preview) system detects and takes action on specific categories of potentially harmful content in both input prompts and output completions. Learn more about Azure AI Content Safety.
Training
Module
Implement generative AI guardrails with Azure AI Content Safety - Training
Learn how to implement generative AI guardrails with Azure AI Content Safety.
Certification
Microsoft Certified: Azure AI Fundamentals - Certifications
Demonstrate fundamental AI concepts related to the development of software and services of Microsoft Azure to create AI solutions.
Documentation
How to use Gretel Navigator chat model with Azure AI Foundry - Azure AI Foundry
Learn how to use Gretel Navigator chat model with Azure AI Foundry.
How to use Jais chat models with Azure AI Foundry - Azure AI Foundry
Learn how to use Jais chat models with Azure AI Foundry.
How to use Cohere Command chat models with Azure AI Foundry - Azure AI Foundry
Learn how to use Cohere Command chat models with Azure AI Foundry.