Skip to content

Commit 6d9b99a

Browse files
committed
Merge branch 'main' into release-usx-pub-preview
2 parents 7d2fde6 + 20d5662 commit 6d9b99a

File tree

144 files changed

+1538
-1775
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

144 files changed

+1538
-1775
lines changed

.openpublishing.redirection.container-service.json

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,10 @@
11
{
22
"redirections": [
3+
{
4+
"source_path_from_root": "/articles/container-service/container-registry-auth-aci.md",
5+
"redirect_url": "/azure/container-service/container-registry-authentication",
6+
"redirect_document_id": false
7+
},
38
{
49
"source_path_from_root": "/articles/container-service/dcos-swarm/container-service-application-specific-marathon.md",
510
"redirect_url": "/previous-versions/azure/container-service/dcos-swarm/container-service-application-specific-marathon",

.openpublishing.redirection.json

Lines changed: 26 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -3909,6 +3909,11 @@
39093909
"redirect_url": "/azure/batch/monitor-batch",
39103910
"redirect_document_id": false
39113911
},
3912+
{
3913+
"source_path_from_root": "/articles/container-registry/container-registry-auth-aci.md",
3914+
"redirect_url": "/azure/container-registry/container-registry-authentication",
3915+
"redirect_document_id": false
3916+
},
39123917
{
39133918
"source_path_from_root": "/articles/event-hubs/move-cluster-across-regions.md",
39143919
"redirect_url": "/azure/operational-excellence/relocation-event-hub-cluster",
@@ -3923,6 +3928,27 @@
39233928
"source_path_from_root": "/articles/defender-for-iot/organizations/update-legacy-ot-software.md",
39243929
"redirect_url": "/azure/defender-for-iot/organizations/update-ot-software?tabs=portal",
39253930
"redirect_document_id": false
3931+
},
3932+
{
3933+
"source_path_from_root":"/articles/virtual-network-manager/concept-user-defined-route-management.md",
3934+
"redirect_url":"/azure/virtual-network-manager/overview",
3935+
"redirect_document_id":false
3936+
3937+
},
3938+
{
3939+
"source_path_from_root":"/articles/virtual-network-manager/how-to-create-user-defined-routes.md",
3940+
"redirect_url":"/azure/virtual-network-manager/overview",
3941+
"redirect_document_id":false
3942+
},
3943+
{
3944+
"source_path_from_root":"/articles/virtual-network-manager/how-to-create-security-admin-rule-network-groups.md",
3945+
"redirect_url":"/azure/virtual-network-manager/overview",
3946+
"redirect_document_id":false
3947+
},
3948+
{
3949+
"source_path_from_root":"/articles/virtual-network-manager/concept-security-admin-rules-network-groups.md",
3950+
"redirect_url":"/azure/virtual-network-manager/overview",
3951+
"redirect_document_id":false
39263952
}
39273953
]
39283954
}

articles/ai-services/openai/toc.yml

Lines changed: 31 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -70,10 +70,6 @@ items:
7070
displayName: PTU, provisioned, provisioned throughput units
7171
- name: System message templates
7272
href: ./concepts/system-message.md
73-
- name: Using your data - text
74-
href: ./concepts/use-your-data.md
75-
- name: Using your data - image (preview)
76-
href: ./concepts/use-your-image-data.md
7773
- name: Legacy models
7874
href: ./concepts/legacy-models.md
7975
- name: How-to
@@ -133,6 +129,16 @@ items:
133129
- name: Function calling
134130
href: ./how-to/fine-tuning-functions.md
135131
displayName: fine-tuning, finetuning
132+
- name: Use your data
133+
items:
134+
- name: Text data
135+
href: ./concepts/use-your-data.md
136+
- name: Image data (preview)
137+
href: ./concepts/use-your-image-data.md
138+
- name: Use Azure OpenAI On Your Data securely
139+
href: ./how-to/use-your-data-securely.md
140+
- name: Deploy and use web apps
141+
href: ./how-to/use-web-app.md
136142
- name: Migrate to OpenAI Python v1.x
137143
href: ./how-to/migration.md
138144
- name: Models
@@ -201,14 +207,27 @@ items:
201207
items:
202208
- name: Assistants API Reference
203209
items:
204-
- name: Assistants
205-
href: ./assistants-reference.md
206-
- name: Threads
207-
href: ./assistants-reference-threads.md
208-
- name: Messages
209-
href: ./assistants-reference-messages.md
210-
- name: Runs
211-
href: ./assistants-reference-runs.md
210+
- name: Python/REST
211+
items:
212+
- name: Assistants
213+
href: ./assistants-reference.md
214+
- name: Threads
215+
href: ./assistants-reference-threads.md
216+
- name: Messages
217+
href: ./assistants-reference-messages.md
218+
- name: Runs
219+
href: ./assistants-reference-runs.md
220+
- name: SDK
221+
items:
222+
- name: C#
223+
href: /dotnet/api/overview/azure/ai.openai.assistants-readme?context=/azure/ai-services/openai/context/context
224+
- name: Go
225+
href: https://pkg.go.dev/github.com/Azure/azure-sdk-for-go/sdk/ai/azopenai
226+
- name: Java
227+
href: /java/api/overview/azure/ai-openai-assistants-readme?context=/azure/ai-services/openai/context/context
228+
- name: JavaScript
229+
href: /javascript/api/overview/azure/openai-assistants-readme?context=/azure/ai-services/openai/context/context
230+
212231
- name: Azure OpenAI On Your Data API Reference
213232
items:
214233
- name: Azure OpenAI On Your Data

articles/aks/TOC.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -849,7 +849,7 @@
849849
- name: Resources
850850
items:
851851
- name: Build your skills with Microsoft Learn training
852-
href: /training/browse/?products=azure-container-instances&azure-container-registry
852+
href: /training/browse/?products=azure-kubernetes-service
853853
- name: Region availability
854854
href: https://azure.microsoft.com/global-infrastructure/services/
855855
- name: Pricing

articles/aks/howto-deploy-java-liberty-app.md

Lines changed: 7 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ description: Deploy a Java application with Open Liberty/WebSphere Liberty on an
55
author: KarlErickson
66
ms.author: edburns
77
ms.topic: how-to
8-
ms.date: 01/16/2024
8+
ms.date: 04/02/2024
99
ms.subservice: aks-developer
1010
keywords: java, jakartaee, javaee, microprofile, open-liberty, websphere-liberty, aks, kubernetes
1111
ms.custom: devx-track-java, devx-track-javaee, devx-track-javaee-liberty, devx-track-javaee-liberty-aks, devx-track-javaee-websphere, build-2023, devx-track-extended-java, devx-track-azurecli
@@ -23,28 +23,24 @@ The Open Liberty Operator simplifies the deployment and management of applicatio
2323

2424
For more information on Open Liberty, see [the Open Liberty project page](https://openliberty.io/). For more information on IBM WebSphere Liberty, see [the WebSphere Liberty product page](https://www.ibm.com/cloud/websphere-liberty).
2525

26-
This article uses the Azure Marketplace offer for Open/WebSphere Liberty to accelerate your journey to AKS. The offer automatically provisions a number of Azure resources including an Azure Container Registry (ACR) instance, an AKS cluster, an Azure App Gateway Ingress Controller (AGIC) instance, the Liberty Operator, and optionally a container image including Liberty and your application. To see the offer, visit the [Azure portal](https://aka.ms/liberty-aks). If you prefer manual step-by-step guidance for running Liberty on AKS that doesn't utilize the automation enabled by the offer, see [Manually deploy a Java application with Open Liberty or WebSphere Liberty on an Azure Kubernetes Service (AKS) cluster](/azure/developer/java/ee/howto-deploy-java-liberty-app-manual).
26+
This article uses the Azure Marketplace offer for Open/WebSphere Liberty to accelerate your journey to AKS. The offer automatically provisions a number of Azure resources including an Azure Container Registry (ACR) instance, an AKS cluster, an Azure App Gateway Ingress Controller (AGIC) instance, the Liberty Operators, and optionally a container image including Liberty and your application. To see the offer, visit the [Azure portal](https://aka.ms/liberty-aks). If you prefer manual step-by-step guidance for running Liberty on AKS that doesn't utilize the automation enabled by the offer, see [Manually deploy a Java application with Open Liberty or WebSphere Liberty on an Azure Kubernetes Service (AKS) cluster](/azure/developer/java/ee/howto-deploy-java-liberty-app-manual).
2727

2828
This article is intended to help you quickly get to deployment. Before going to production, you should explore [Tuning Liberty](https://www.ibm.com/docs/was-liberty/base?topic=tuning-liberty).
2929

3030
[!INCLUDE [quickstarts-free-trial-note](../../includes/quickstarts-free-trial-note.md)]
3131

32-
* You can use Azure Cloud Shell or a local terminal.
33-
3432
[!INCLUDE [azure-cli-prepare-your-environment.md](~/reusable-content/azure-cli/azure-cli-prepare-your-environment.md)]
3533

36-
* This article requires at least version 2.31.0 of Azure CLI. If using Azure Cloud Shell, the latest version is already installed.
37-
3834
> [!NOTE]
3935
> You can also execute this guidance from the [Azure Cloud Shell](/azure/cloud-shell/quickstart). This approach has all the prerequisite tools pre-installed, with the exception of Docker.
4036
>
4137
> :::image type="icon" source="~/reusable-content/ce-skilling/azure/media/cloud-shell/launch-cloud-shell-button.png" alt-text="Button to launch the Azure Cloud Shell." border="false" link="https://shell.azure.com":::
4238
43-
* If running the commands in this guide locally (instead of Azure Cloud Shell):
44-
* Prepare a local machine with Unix-like operating system installed (for example, Ubuntu, Azure Linux, macOS, Windows Subsystem for Linux).
45-
* Install a Java SE implementation, version 17 or later. (for example, [Eclipse Open J9](https://www.eclipse.org/openj9/)).
46-
* Install [Maven](https://maven.apache.org/download.cgi) 3.5.0 or higher.
47-
* Install [Docker](https://docs.docker.com/get-docker/) for your OS.
39+
* Prepare a local machine with a Unix-like operating system installed (for example, Ubuntu, macOS, Windows Subsystem for Linux).
40+
* This article requires at least version 2.31.0 of Azure CLI.
41+
* Install a Java SE implementation, version 17 or later. (for example, [Eclipse Open J9](https://www.eclipse.org/openj9/)).
42+
* Install [Maven](https://maven.apache.org/download.cgi) 3.5.0 or higher.
43+
* Install [Docker](https://docs.docker.com/get-docker/) for your OS.
4844
* Make sure you're assigned either the `Owner` role or the `Contributor` and `User Access Administrator` roles in the subscription. You can verify it by following steps in [List role assignments for a user or group](../role-based-access-control/role-assignments-list-portal.md#list-role-assignments-for-a-user-or-group).
4945

5046
## Create a Liberty on AKS deployment using the portal

articles/aks/limit-egress-traffic.md

Lines changed: 2 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ ms.subservice: aks-networking
55
ms.custom: devx-track-azurecli
66
ms.topic: how-to
77
ms.author: allensu
8-
ms.date: 12/05/2023
8+
ms.date: 04/02/2024
99
author: asudbring
1010
#Customer intent: As a cluster operator, I want to restrict egress traffic for nodes to only access defined ports and addresses and improve cluster security.
1111
---
@@ -178,8 +178,7 @@ For information on how to override Azure's default system routes or add addition
178178
This section covers three network rules and an application rule you can use to configure on your firewall. You may need to adapt these rules based on your deployment.
179179
180180
* The first network rule allows access to port 9000 via TCP.
181-
* The second network rule allows access to port 1194 and 123 via UDP. If you're deploying to Microsoft Azure operated by 21Vianet, see the [Azure operated by 21Vianet required network rules](./outbound-rules-control-egress.md#microsoft-azure-operated-by-21vianet-required-network-rules). Both these rules will only allow traffic destined to the Azure Region CIDR in this article, which is East US.
182-
* The third network rule opens port 123 to `ntp.ubuntu.com` FQDN via UDP. Adding an FQDN as a network rule is one of the specific features of Azure Firewall, so you'll need to adapt it when using your own options.
181+
* The second network rule allows access to port 1194 via UDP. If you're deploying to Microsoft Azure operated by 21Vianet, see the [Azure operated by 21Vianet required network rules](./outbound-rules-control-egress.md#microsoft-azure-operated-by-21vianet-required-network-rules). Both these rules will only allow traffic destined to the Azure Region CIDR in this article, which is East US.
183182
* The fourth and fifth network rules allow access to pull containers from GitHub Container Registry (ghcr.io) and Docker Hub (docker.io).
184183
185184
1. Create the network rules using the [`az network firewall network-rule create`][az-network-firewall-network-rule-create] command.
@@ -189,8 +188,6 @@ This section covers three network rules and an application rule you can use to c
189188
190189
az network firewall network-rule create -g $RG -f $FWNAME --collection-name 'aksfwnr' -n 'apitcp' --protocols 'TCP' --source-addresses '*' --destination-addresses "AzureCloud.$LOC" --destination-ports 9000
191190
192-
az network firewall network-rule create -g $RG -f $FWNAME --collection-name 'aksfwnr' -n 'time' --protocols 'UDP' --source-addresses '*' --destination-fqdns 'ntp.ubuntu.com' --destination-ports 123
193-
194191
az network firewall network-rule create -g $RG -f $FWNAME --collection-name 'aksfwnr' -n 'ghcr' --protocols 'TCP' --source-addresses '*' --destination-fqdns ghcr.io pkg-containers.githubusercontent.com --destination-ports '443'
195192
196193
az network firewall network-rule create -g $RG -f $FWNAME --collection-name 'aksfwnr' -n 'docker' --protocols 'TCP' --source-addresses '*' --destination-fqdns docker.io registry-1.docker.io production.cloudflare.docker.com --destination-ports '443'

articles/api-management/configure-custom-domain.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -105,6 +105,7 @@ API Management offers a free, managed TLS certificate for your domain, if you do
105105
* Not supported in the following Azure regions: France South and South Africa West
106106
* Currently available only in the Azure cloud
107107
* Does not support root domain names (for example, `contoso.com`). Requires a fully qualified name such as `api.contoso.com`.
108+
* Supports only public domain names
108109
* Can only be configured when updating an existing API Management instance, not when creating an instance
109110

110111

articles/app-service/quickstart-python.md

Lines changed: 60 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -59,6 +59,66 @@ To run the application locally:
5959
pip install -r requirements.txt
6060
```
6161

62+
1. Integrate a database:
63+
64+
```Python
65+
66+
from azure.cosmos.aio import CosmosClient
67+
from azure.cosmos import exceptions
68+
from azure.cosmos.partition_key import PartitionKey
69+
70+
from configs.credential import HOST, MASTER_KEY, DATABASE_ID
71+
72+
73+
def get_database_client():
74+
# Initialize the Cosmos client
75+
client = CosmosClient(HOST, MASTER_KEY)
76+
77+
# Create or get a reference to a database
78+
try:
79+
database = client.create_database_if_not_exists(id=DATABASE_ID)
80+
print(f'Database "{DATABASE_ID}" created or retrieved successfully.')
81+
82+
except exceptions.CosmosResourceExistsError:
83+
database = client.get_database_client(DATABASE_ID)
84+
print('Database with id \'{0}\' was found'.format(DATABASE_ID))
85+
86+
return database
87+
88+
89+
def get_container_client(container_id):
90+
database = get_database_client()
91+
# Create or get a reference to a container
92+
try:
93+
container = database.create_container(id=container_id, partition_key=PartitionKey(path='/partitionKey'))
94+
print('Container with id \'{0}\' created'.format(container_id))
95+
96+
except exceptions.CosmosResourceExistsError:
97+
container = database.get_container_client(container_id)
98+
print('Container with id \'{0}\' was found'.format(container_id))
99+
100+
return container
101+
102+
async def create_item(container_id, item):
103+
async with CosmosClient(HOST, credential=MASTER_KEY) as client:
104+
database = client.get_database_client(DATABASE_ID)
105+
container = database.get_container_client(container_id)
106+
await container.upsert_item(body=item)
107+
108+
async def get_items(container_id):
109+
items = []
110+
try:
111+
async with CosmosClient(HOST, credential=MASTER_KEY) as client:
112+
database = client.get_database_client(DATABASE_ID)
113+
container = database.get_container_client(container_id)
114+
async for item in container.read_all_items():
115+
items.append(item)
116+
except Exception as e:
117+
print(f"An error occurred: {e}")
118+
119+
return items
120+
```
121+
62122
1. Run the app:
63123

64124
```Console

articles/azure-functions/TOC.yml

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -451,10 +451,10 @@
451451
href: functions-create-maven-kotlin-intellij.md
452452
- name: Linux App Service plan
453453
href: create-function-app-linux-app-service-plan.md
454-
- name: Linux Consumption plan
455-
href: create-first-function-cli-python.md
454+
- name: Consumption plan
455+
href: ./scripts/functions-cli-create-app-service-plan.md
456456
- name: Premium plan
457-
href: create-premium-plan-function-app-portal.md
457+
href: ./scripts/functions-cli-create-premium-plan.md
458458
- name: Linux container (Premium)
459459
href: functions-deploy-container.md
460460
displayName: container, Docker, custom

articles/azure-functions/durable/quickstart-js-vscode.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -289,10 +289,10 @@ After you've verified that the function runs correctly on your local computer, i
289289
::: zone-end
290290

291291
::: zone pivot="nodejs-model-v3"
292-
1. Copy the URL of the HTTP trigger from the **Output** panel. The URL that calls your HTTP-triggered function should be in this format: `http://<functionappname>.azurewebsites.net/api/orchestrators/HelloOrchestrator`
292+
1. Copy the URL of the HTTP trigger from the **Output** panel. The URL that calls your HTTP-triggered function should be in this format: `https://<functionappname>.azurewebsites.net/api/orchestrators/HelloOrchestrator`
293293
::: zone-end
294294
::: zone pivot="nodejs-model-v4"
295-
1. Copy the URL of the HTTP trigger from the **Output** panel. The URL that calls your HTTP-triggered function should be in this format: `http://<functionappname>.azurewebsites.net/api/orchestrators/helloOrchestrator`
295+
1. Copy the URL of the HTTP trigger from the **Output** panel. The URL that calls your HTTP-triggered function should be in this format: `https://<functionappname>.azurewebsites.net/api/orchestrators/helloOrchestrator`
296296
::: zone-end
297297

298298
2. Paste this new URL for the HTTP request into your browser's address bar. You should get the same status response as before when using the published app.

0 commit comments

Comments
 (0)