Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Azure Container Apps allows you to run containerized applications without worrying about orchestration or infrastructure.
Azure Container Apps is a serverless platform that allows you to maintain less infrastructure and save costs while running containerized applications. Instead of worrying about server configuration, container orchestration, and deployment details, Container Apps provides all the up-to-date server resources required to keep your applications stable and secure. For a more detailed overview, see the Azure Container Apps product page.
Azure Container Apps dynamic sessions
Azure Container Apps dynamic sessions are like having a bunch of secure, ready-to-go mini-computers that start up super fast whenever you need them. You can access these sessions easily through data-plane REST APIs, and they automatically clean up after themselves when you’re done. There are two main types: one for running code safely with pre-installed tools called Code-Interpreter sessions, and another for using your own custom setups called Custom Container sessions. More details on dynamic sessions can be found at: Azure Container Apps dynamic sessions overview
Common Azure Container Apps dynamic sessions request headers
The following request headers are common:
| Header | Required | Type | Description |
|---|---|---|---|
| Authorization | Required | String | Provide a valid bearer token for authorized API calls. You might need to clear your browser cache if you tried unauthenticated calls before. |
| Content-Type | Required (on POST) | String | It must be application/json. |
| operation-id | Not required | String | The ID of this execution operation. |
Common Azure Container Apps dynamic sessions response headers
The following response headers are common:
| Header | Description |
|---|---|
| Content-Type | The Content-Type is application/json. |
| Date | The date time of the response operation. This date time format conforms to the RFC 1123 date time format expressed in Coordinated Universal Time. |
| operation-id | The unique identifier for the operation. |
| Operation-Location | The URL where the status of the operation can be checked. |
| x-ms-execution-request-time | The time taken to execute the request in milliseconds. |
| x-ms-execution-read-response-time | The time taken to read the response in milliseconds. |
| x-ms-total-execution-service-time | The total time taken for the execution service in milliseconds. |
| x-ms-session-guid | The unique identifier for the session. |
| x-ms-container-execution-duration | The duration of container execution in milliseconds. |
| x-ms-preparation-time | The time taken for preparation in milliseconds. |
| x-ms-allocation-retries | The number of retries for allocation. |
| x-ms-allocation-time | The time taken for allocation in milliseconds. |
| x-ms-overall-execution-time | The overall execution time in milliseconds. |
Data plane REST APIs
| Operation group | Description |
|---|---|
| Code Execution | Execute and Get code execution in a session |
| Session Resource Files | Upload, List, Get, Get Content, Delete a file resource in a session |