You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
> We don't recommend using preview models in production. We will upgrade all deployments of preview models to either future preview versions or to the latest stable/GA version. Models designated preview do not follow the standard Azure OpenAI model lifecycle.
@@ -76,14 +76,20 @@ See [model versions](../concepts/model-versions.md) to learn about how Azure Ope
76
76
77
77
GPT-3.5 models can understand and generate natural language or code. The most capable and cost effective model in the GPT-3.5 family is GPT-3.5 Turbo, which has been optimized for chat and works well for traditional completions tasks as well. GPT-3.5 Turbo is available for use with the Chat Completions API. GPT-3.5 Turbo Instruct has similar capabilities to `text-davinci-003` using the Completions API instead of the Chat Completions API. We recommend using GPT-3.5 Turbo and GPT-3.5 Turbo Instruct over [legacy GPT-3.5 and GPT-3 models](./legacy-models.md).
78
78
79
-
-`gpt-35-turbo`
80
-
-`gpt-35-turbo-16k`
81
-
-`gpt-35-turbo-instruct`
82
79
83
-
You can see the token context length supported by each model in the [model summary table](#model-summary-table-and-region-availability).
80
+
| Model ID | Description | Max Request (tokens) | Training Data (up to) |
81
+
| --------- |:---|:------:|:----:|
82
+
|`gpt-35-turbo` (0125) **NEW**|**Latest GA Model** <br> - JSON Mode <br> - parallel function calling <br> - reproducible output (preview) <br> - Higher accuracy at responding in requested formats. <br> - Fix for a bug which caused a text encoding issue for non-English language function calls. | Input: 16,385<br> Output: 4,096 | Sep 2021 |
To learn more about how to interact with GPT-3.5 Turbo and the Chat Completions API check out our [in-depth how-to](../how-to/chatgpt.md).
86
90
91
+
**<sup>1</sup>** This model will accept requests > 4,096 tokens. It is not recommended to exceed the 4,096 input token limit as the newer version of the model are capped at 4,096 tokens. If you encounter issues when exceeding 4,096 input tokens with this model this configuration is not officially supported.
92
+
87
93
## Embeddings
88
94
89
95
`text-embedding-3-large` is the latest and most capable embedding model. Upgrading between embeddings models is not possible. In order to move from using `text-embedding-ada-002` to `text-embedding-3-large` you would need to generate new embeddings.
@@ -184,23 +190,12 @@ See [model versions](../concepts/model-versions.md) to learn about how Azure Ope
184
190
> [!NOTE]
185
191
> Version `0613` of `gpt-35-turbo` and `gpt-35-turbo-16k` will be retired no earlier than August 1, 2024. Version `0301` of `gpt-35-turbo` will be retired no earlier than August 1, 2024. See [model updates](../how-to/working-with-models.md#model-updates) for model upgrade behavior.
186
192
187
-
| Model ID | Max Request (tokens) | Training Data (up to) |
**<sup>1</sup>** This model will accept requests > 4,096 tokens. It is not recommended to exceed the 4,096 input token limit as the newer version of the model are capped at 4,096 tokens. If you encounter issues when exceeding 4,096 input tokens with this model this configuration is not officially supported.
203
-
204
199
#### Azure Government regions
205
200
206
201
The following GPT-3.5 turbo models are available with [Azure Government](/azure/azure-government/documentation-government-welcome):
Copy file name to clipboardExpand all lines: articles/azure-app-configuration/quickstart-bicep.md
+5-2Lines changed: 5 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,6 +28,9 @@ If you don't have an Azure subscription, create a [free account](https://azure.m
28
28
29
29
Managing an Azure App Configuration resource with Bicep file requires an Azure Resource Manager role, such as contributor or owner. Accessing Azure App Configuration data (key-values, snapshots) requires an Azure Resource Manager role and an additional Azure App Configuration [data plane role](concept-enable-rbac.md) when the configuration store's ARM authentication mode is set to [pass-through](./quickstart-deployment-overview.md#azure-resource-manager-authentication-mode) ARM authentication mode.
30
30
31
+
> [!IMPORTANT]
32
+
> Configuring ARM authentication mode requires App Configuration control plane API version `2023-08-01-preview` or later.
33
+
31
34
## Review the Bicep file
32
35
33
36
The Bicep file used in this quickstart is from [Azure Quickstart Templates](https://azure.microsoft.com/resources/templates/app-configuration-store-kv/).
@@ -39,8 +42,8 @@ The Bicep file used in this quickstart is from [Azure Quickstart Templates](http
39
42
40
43
Two Azure resources are defined in the Bicep file:
41
44
42
-
-[Microsoft.AppConfiguration/configurationStores](/azure/templates/microsoft.appconfiguration/2020-07-01-preview/configurationstores): create an App Configuration store.
43
-
-[Microsoft.AppConfiguration/configurationStores/keyValues](/azure/templates/microsoft.appconfiguration/2020-07-01-preview/configurationstores/keyvalues): create a key-value inside the App Configuration store.
45
+
-[Microsoft.AppConfiguration/configurationStores](/azure/templates/microsoft.appconfiguration/configurationstores): create an App Configuration store.
46
+
-[Microsoft.AppConfiguration/configurationStores/keyValues](/azure/templates/microsoft.appconfiguration/configurationstores/keyvalues): create a key-value inside the App Configuration store.
44
47
45
48
With this Bicep file, we create one key with two different values, one of which has a unique label.
Copy file name to clipboardExpand all lines: articles/azure-app-configuration/quickstart-deployment-overview.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -33,6 +33,9 @@ To learn more about Azure RBAC and Microsoft Entra ID, see [Authorize access to
33
33
34
34
Azure App Configuration data, such as key-values and snapshots, can be managed in deployment. When managing App Configuration data using this method, it's recommended to set your configuration store's Azure Resource Manager authentication mode to **Pass-through**. This authentication mode ensures that data access requires a combination of data plane and Azure Resource Manager management roles and ensuring that data access can be properly attributed to the deployment caller for auditing purpose.
35
35
36
+
> [!IMPORTANT]
37
+
> App Configuration control plane API version `2023-08-01-preview` or later is required to configure **Azure Resource Manager Authentication Mode** using [ARM template](./quickstart-resource-manager.md), [Bicep](./quickstart-bicep.md), or REST API. See the [REST API examples](https://github.com/Azure/azure-rest-api-specs/blob/main/specification/appconfiguration/resource-manager/Microsoft.AppConfiguration/preview/2023-08-01-preview/examples/ConfigurationStoresCreateWithDataPlaneProxy.json).
Copy file name to clipboardExpand all lines: articles/azure-app-configuration/quickstart-resource-manager.md
+6-3Lines changed: 6 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -35,21 +35,24 @@ If you don't have an Azure subscription, create a [free account](https://azure.m
35
35
36
36
Managing Azure App Configuration resource inside an ARM template requires Azure Resource Manager role, such as contributor or owner. Accessing Azure App Configuration data (key-values, snapshots) requires Azure Resource Manager role and Azure App Configuration [data plane role](concept-enable-rbac.md) under [pass-through](./quickstart-deployment-overview.md#azure-resource-manager-authentication-mode) ARM authentication mode.
37
37
38
+
> [!IMPORTANT]
39
+
> Configuring ARM authentication mode requires App Configuration control plane API version `2023-08-01-preview` or later.
40
+
38
41
## Review the template
39
42
40
43
The template used in this quickstart is from [Azure Quickstart Templates](https://azure.microsoft.com/resources/templates/app-configuration-store-kv/). It creates a new App Configuration store with two key-values inside. It then uses the `reference` function to output the values of the two key-value resources. Reading the key's value in this way allows it to be used in other places in the template.
41
44
42
45
The quickstart uses the `copy` element to create multiple instances of key-value resource. To learn more about the `copy` element, see [Resource iteration in ARM templates](../azure-resource-manager/templates/copy-resources.md).
43
46
44
47
> [!IMPORTANT]
45
-
> This template requires App Configuration resource provider version `2020-07-01-preview` or later. This version uses the `reference` function to read key-values. The `listKeyValue` function that was used to read key-values in the previous version is not available starting in version `2020-07-01-preview`.
48
+
> This template requires App Configuration control plane API version `2022-05-01` or later. This version uses the `reference` function to read key-values. The `listKeyValue` function that was used to read key-values in the previous version is not available starting in version `2020-07-01-preview`.
-[Microsoft.AppConfiguration/configurationStores](/azure/templates/microsoft.appconfiguration/2020-07-01-preview/configurationstores): create an App Configuration store.
52
-
-[Microsoft.AppConfiguration/configurationStores/keyValues](/azure/templates/microsoft.appconfiguration/2020-07-01-preview/configurationstores/keyvalues): create a key-value inside the App Configuration store.
54
+
-[Microsoft.AppConfiguration/configurationStores](/azure/templates/microsoft.appconfiguration/configurationstores): create an App Configuration store.
55
+
-[Microsoft.AppConfiguration/configurationStores/keyValues](/azure/templates/microsoft.appconfiguration/configurationstores/keyvalues): create a key-value inside the App Configuration store.
53
56
54
57
> [!TIP]
55
58
> The `keyValues` resource's name is a combination of key and label. The key and label are joined by the `$` delimiter. The label is optional. In the above example, the `keyValues` resource with name `myKey` creates a key-value without a label.
With Bicep CLI version 0.27.1 or newer, you can publish a module with the Bicep source code in addition to the compiled JSON template. If a module is published with the Bicep source code to a registry, you can press `F12` ([Go to Definition](./visual-studio-code.md#go-to-definition)) from Visual Studio Code to see the Bicep Code. The Bicep extension version 0.27 or new is required to see the Bicep file.
To run this deployment command, you must have the [latest version](/cli/azure/install-azure-cli) of Azure CLI.
87
+
88
+
```azurecli
89
+
az bicep publish --file storage.bicep --target br:exampleregistry.azurecr.io/bicep/modules/storage:v1 --documentationUri https://www.contoso.com/exampleregistry.html --with-source
90
+
```
91
+
92
+
---
93
+
94
+
With the with source switch, you see an additional layer in the manifest:
95
+
96
+
:::image type="content" source="./media/private-module-registry/bicep-module-with-source-manifest.png" lightbox="./media/private-module-registry/bicep-module-with-source-manifest.png" alt-text="Screenshot of bicep module registry with source.":::
97
+
98
+
Note that if the Bicep module references a module in a Private Registry, the ACR endpoint will be visible. To hide the full endpoint, you can configure an alias for the private registry.
99
+
76
100
## View files in registry
77
101
78
102
To see the published module in the portal:
79
103
80
104
1. Sign in to the [Azure portal](https://portal.azure.com).
81
105
1. Search for **container registries**.
82
106
1. Select your registry.
83
-
1. Select **Repositories** from the left menu.
107
+
1. Select **Services** -> **Repositories** from the left menu.
84
108
1. Select the module path (repository). In the preceding example, the module path name is **bicep/modules/storage**.
85
109
1. Select the tag. In the preceding example, the tag is **v1**.
86
110
1. The **Artifact reference** matches the reference you'll use in the Bicep file.
0 commit comments