Skip to content

Commit ab5ab0f

Browse files
ttorblettorble
authored
Merge pull request #258897 from MicrosoftDocs/main
Publish to live, Friday 4 AM PST, 11/17
2 parents bc40cd4 + e0f42d4 commit ab5ab0f

File tree

40 files changed

+1608
-766
lines changed

40 files changed

+1608
-766
lines changed

‎articles/ai-services/speech-service/batch-transcription.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -35,7 +35,8 @@ To use the batch transcription REST API:
3535
1. [Create a batch transcription](batch-transcription-create.md) - Submit the transcription job with parameters such as the audio files, the transcription language, and the transcription model.
3636
1. [Get batch transcription results](batch-transcription-get.md) - Check transcription status and retrieve transcription results asynchronously.
3737

38-
Batch transcription jobs are scheduled on a best-effort basis. You can't estimate when a job will change into the running state, but it should happen within minutes under normal system load. When the job is in the running state, the transcription occurs faster than the audio runtime playback speed.
38+
> [!IMPORTANT]
39+
> Batch transcription jobs are scheduled on a best-effort basis. At pick hours it may take up to 30 minutes or longer for a transcription job to start processing. See how to check the current status of a batch transcription job in [this section](batch-transcription-get.md#get-transcription-status).
3940
4041
## Next steps
4142

‎articles/cosmos-db/priority-based-execution.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -106,6 +106,7 @@ container.createItem(family, new PartitionKey(family.getLastName()), requestOpti
106106
}).subscribe();
107107

108108
```
109+
---
109110

110111
## Monitoring Priority-based execution
111112

‎articles/mysql/flexible-server/concepts-high-availability.md

Lines changed: 4 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -82,7 +82,7 @@ The overall failover time depends on the current workload and the last checkpoin
8282
> [!NOTE]
8383
>Azure Resource Health event is generated in the event of planned failover, representing the failover time during which server was unavailable. The triggered events can be seen when clicked on "Resource Health" in the left pane. User initiated/ Manual failover is represented by status as **"Unavailable"** and tagged as **"Planned"**. Example - "A failover operation was triggered by an authorized user (Planned)". If your resource remains in this state for an extended period of time, please open a [support ticket](https://azure.microsoft.com/support/create-ticket/) and we will assist you.
8484
85-
85+
8686
### Unplanned: Automatic failover
8787

8888
Unplanned service downtime can be caused by software bugs or infrastructure faults like compute, network, or storage failures, or power outages that affect the availability of the database. If the database becomes unavailable, replication to the standby replica is severed and the standby replica is activated as the primary database. DNS is updated, and clients reconnect to the database server and resume their operations.
@@ -122,8 +122,8 @@ Here are some considerations to keep in mind when you use high availability:
122122
- Zone-redundant high availability can be set only when the flexible server is created.
123123
- High availability isn't supported in the burstable compute tier.
124124
- Restarting the primary database server to pick up static parameter changes also restarts the standby replica.
125-
- Data-in Replication isn't supported for HA servers.
126125
- GTID mode will be turned on as the HA solution uses GTID. Check whether your workload has [restrictions or limitations on replication with GTIDs](https://dev.mysql.com/doc/refman/5.7/en/replication-gtids-restrictions.html).
126+
127127
>[!Note]
128128
>If you are enabling same-zone HA post the server create, you need to make sure the server parameters enforce_gtid_consistency” and [“gtid_mode”](./concepts-read-replicas.md#global-transaction-identifier-gtid) is set to ON before enabling HA.
129129
@@ -176,13 +176,7 @@ You need to be able to mitigate downtime for your application even when you're n
176176
Yes, read replicas are supported for HA servers.</br>
177177

178178
- **Can I use Data-in Replication for HA servers?**</br>
179-
Data-in Replication isn't supported for HA servers. But Data-in Replication for HA servers is on our roadmap and will be available soon. For now, if you want to use Data-in Replication for migration, you can follow these steps:
180-
1. Create the server with zone-redundant HA enabled.
181-
1. Disable HA.
182-
1. Complete the steps to [set up Data-in Replication](./concepts-data-in-replication.md). (Be sure `gtid_mode` has the same setting on the source and target servers.)
183-
1. Post cutovers remove the Data-in Replication configuration.
184-
1. Enable HA.
185-
179+
Yes, support for data-in replication for high availability (HA) enabled server is available only through GTID-based replication.
186180
- **To reduce downtime, can I fail over to the standby server during server restarts or while scaling up or down?** </br>
187181
Currently, Azure MySQL Flexible Server has utlized Planned Failover to optmize the HA operations including scaling up/down, and planned maintenance to help reduce the downtime.
188182
When such operations started, it would operate on the original standby instance first, followed by triggering a planned failover operation, and then operate on the original primary instance. </br>
@@ -195,3 +189,4 @@ If you create the server with Zone-redundant HA mode enabled then you can change
195189
- Learn about [business continuity](./concepts-business-continuity.md).
196190
- Learn about [zone-redundant high availability](./concepts-high-availability.md).
197191
- Learn about [backup and recovery](./concepts-backup-restore.md).
192+

‎articles/service-connector/concept-service-connector-internals.md

Lines changed: 5 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,6 @@ ms.custom: event-tier1-build-2022, engagement-fy23
88
ms.topic: conceptual
99
ms.date: 01/17/2023
1010
---
11-
1211
# Service Connector internals
1312

1413
Service Connector is an Azure extension resource provider designed to provide a simple way to create and manage connections between Azure services.
@@ -25,11 +24,11 @@ Service Connector offers the following features:
2524
The concept of *service connection* is a key concept in the resource model of Service Connector. A service connection represents an abstraction of the link between two services. Service connections have the following properties:
2625

2726
| Property | Description |
28-
|---------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
27+
| ------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
2928
| Connection Name | The unique name of the service connection. |
30-
| Source Service Type | Source services are services you can connect to target services. They are usually Azure compute services and they include Azure App Service, Azure Container Apps and Azure Spring Apps. |
29+
| Source Service Type | Source services are services you can connect to target services. They are usually Azure compute services and they include Azure App Service, Azure Functions, Azure Container Apps and Azure Spring Apps.
3130
| Target Service Type | Target services are backing services or dependency services that your compute services connect to. Service Connector supports various target service types including major databases, storage, real-time services, state, and secret stores. |
32-
| Client Type | Client type refers to your compute runtime stack, development framework, or specific type of client library that accepts the specific format of the connection environment variables or properties. |
31+
| Client Type | Client type refers to your compute runtime stack, development framework, or specific type of client library that accepts the specific format of the connection environment variables or properties. |
3332
| Authentication Type | The authentication type used for the service connection. It could be a secret/connection string, a managed identity, or a service principal. |
3433

3534
Source services and target services support multiple simultaneous service connections, which means that you can connect each resource to multiple resources.
@@ -89,8 +88,8 @@ az containerapp connection list-configuration --resource-group <source-service-r
8988
Service Connector sets the connection configuration when creating a connection. The environment variable key-value pairs are determined based on your client type and authentication type. For example, using the Azure SDK with a managed identity requires a client ID, client secret, etc. Using a JDBC driver requires a database connection string. Follow these conventions to name the configurations:
9089

9190
- Spring Boot client: the Spring Boot library for each target service has its own naming convention. For example, MySQL connection settings would be `spring.datasource.url`, `spring.datasource.username`, `spring.datasource.password`. Kafka connection settings would be `spring.kafka.properties.bootstrap.servers`.
92-
9391
- Other clients:
92+
9493
- The key name of the first connection configuration uses the format `<Cloud>_<Type>_<Name>`. For example, `AZURE_STORAGEBLOB_RESOURCEENDPOINT`, `CONFLUENTCLOUD_KAFKA_BOOTSTRAPSERVER`.
9594
- For the same type of target resource, the key name of the second connection configuration uses the format `<Cloud>_<Type>_<Connection Name>_<Name>`. For example, `AZURE_STORAGEBLOB_CONN2_RESOURCEENDPOINT`, `CONFLUENTCLOUD_KAFKA_CONN2_BOOTSTRAPSERVER`.
9695

@@ -110,7 +109,7 @@ Service Connector offers three network solutions for users to choose from when c
110109
- The compute resource must have virtual network integration enabled. For Azure App Service, it can be configured in its networking settings; for Azure Spring Apps, users must set VNet injection during the resource creation stage.
111110
- The target service must support private endpoints. For a list of supported services, refer to [Private-link resource](/azure/private-link/private-endpoint-overview#private-link-resource).
112111

113-
When selecting this option, Service Connector doesn't perform any more configurations in the compute or target resources. Instead, it verifies the existence of a valid private endpoint and fails the connection if not found. For convenience, users can select the "New Private Endpoint" checkbox in the Azure Portal when creating a connection. With it, Service Connector automatically creates all related resources for the private endpoint in the proper sequence, simplifying the connection creation process.
112+
When selecting this option, Service Connector doesn't perform any more configurations in the compute or target resources. Instead, it verifies the existence of a valid private endpoint and fails the connection if not found. For convenience, users can select the "New Private Endpoint" checkbox in the Azure portal when creating a connection. With it, Service Connector automatically creates all related resources for the private endpoint in the proper sequence, simplifying the connection creation process.
114113

115114

116115

‎articles/service-connector/how-to-integrate-app-configuration.md

Lines changed: 9 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -7,20 +7,21 @@ ms.service: service-connector
77
ms.topic: how-to
88
ms.date: 10/26/2023
99
---
10-
1110
# Integrate Azure App Configuration with Service Connector
1211

1312
This page shows supported authentication methods and clients, and shows sample code you can use to connect Azure App Configuration to other cloud services using Service Connector. You might still be able to connect to App Configuration using other methods. This page also shows default environment variable names and values you get when you create the service connection.
1413

1514
## Supported compute services
1615

1716
- Azure App Service
17+
- Azure Functions
1818
- Azure Container Apps
1919
- Azure Spring Apps
2020

2121
## Supported authentication types and client types
2222

23-
Supported authentication and clients for App Service, Container Apps and Azure Spring Apps:
23+
Supported authentication and clients for App Service, Azure Functions, Container Apps and Azure Spring Apps:
24+
2425

2526
| Client type | System-assigned managed identity | User-assigned managed identity | Secret/connection string | Service principal |
2627
|-------------|:------------------------------------:|:------------------------------------:|:------------------------------------:|:------------------------------------:|
@@ -38,8 +39,8 @@ Use the connection details below to connect compute services to Azure App Config
3839

3940
### System-assigned managed identity
4041

41-
| Default environment variable name | Description | Sample value |
42-
|-----------------------------------|------------------------------|------------------------------------------------|
42+
| Default environment variable name | Description | Sample value |
43+
| --------------------------------- | ---------------------------- | ------------------------------------------------ |
4344
| AZURE_APPCONFIGURATION_ENDPOINT | App Configuration endpoint | `https://<App-Configuration-name>.azconfig.io` |
4445

4546
#### Sample code
@@ -48,8 +49,8 @@ Refer to the steps and code below to connect to Azure App Configuration using a
4849

4950
### User-assigned managed identity
5051

51-
| Default environment variable name | Description | Sample value |
52-
|-----------------------------------|----------------------------|-----------------------------------------------|
52+
| Default environment variable name | Description | Sample value |
53+
| --------------------------------- | -------------------------- | ----------------------------------------------- |
5354
| AZURE_APPCONFIGURATION_ENDPOINT | App Configuration Endpoint | `https://App-Configuration-name>.azconfig.io` |
5455
| AZURE_APPCONFIGURATION_CLIENTID | Your client ID | `<client-ID>` |
5556

@@ -71,8 +72,8 @@ Refer to the steps and code below to connect to Azure App Configuration using a
7172

7273
### Service principal
7374

74-
| Default environment variable name | Description | Sample value |
75-
|-------------------------------------|----------------------------|----------------------------------------------|
75+
| Default environment variable name | Description | Sample value |
76+
| ----------------------------------- | -------------------------- | ---------------------------------------------- |
7677
| AZURE_APPCONFIGURATION_ENDPOINT | App Configuration Endpoint | `https://<AppConfigurationName>.azconfig.io` |
7778
| AZURE_APPCONFIGURATION_CLIENTID | Your client ID | `<client-ID>` |
7879
| AZURE_APPCONFIGURATION_CLIENTSECRET | Your client secret | `<client-secret>` |

‎articles/service-connector/how-to-integrate-confluent-kafka.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -8,23 +8,23 @@ ms.topic: how-to
88
ms.date: 11/07/2023
99
ms.custom: event-tier1-build-2022
1010
---
11-
1211
# Integrate Apache Kafka on Confluent Cloud with Service Connector
1312

1413
This page shows supported authentication methods and clients to connect Apache Kafka on Confluent Cloud to other cloud services using Service Connector. You might still be able to connect to Apache Kafka on Confluent Cloud in other programming languages without using Service Connector. This page also shows default environment variable names and values (or Spring Boot configuration) you get when you create the service connection.
1514

1615
## Supported compute services
1716

1817
- Azure App Service
18+
- Azure Functions
1919
- Azure Container Apps
2020
- Azure Spring Apps
2121

2222
## Supported Authentication types and client types
2323

24-
Supported authentication and clients for App Service, Container Apps and Azure Spring Apps:
24+
Supported authentication and clients for App Service, Azure Functions, Container Apps and Azure Spring Apps:
2525

26-
| Client type | System-assigned managed identity | User-assigned managed identity | Secret / connection string | Service principal |
27-
|--------------------|----------------------------------|--------------------------------|--------------------------------------|-------------------|
26+
| Client type | System-assigned managed identity | User-assigned managed identity | Secret / connection string | Service principal |
27+
| ------------------ | -------------------------------- | ------------------------------ | ---------------------------------- | ----------------- |
2828
| .NET | | | ![yes icon](./media/green-check.png) | |
2929
| Java | | | ![yes icon](./media/green-check.png) | |
3030
| Java - Spring Boot | | | ![yes icon](./media/green-check.png) | |
@@ -40,8 +40,8 @@ Use the connection details below to connect compute services to Kafka. For each
4040

4141
#### SpringBoot client type
4242

43-
| Default environment variable name | Description | Example value |
44-
|--------------------------------------------------------------|------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------|
43+
| Default environment variable name | Description | Example value |
44+
| ------------------------------------------------------------ | ---------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- |
4545
| spring.kafka.properties.bootstrap.servers | Your Kafka bootstrap server | `pkc-<server-name>.eastus.azure.confluent.cloud:9092` |
4646
| spring.kafka.properties.sasl.jaas.config | Your Kafka SASL configuration | `org.apache.kafka.common.security.plain.PlainLoginModule required username='<Bootstrap-server-key>' password='<Bootstrap-server-secret>';` |
4747
| spring.kafka.properties.schema.registry.url | Your Confluent registry URL | `https://psrc-<server-name>.westus2.azure.confluent.cloud` |

0 commit comments

Comments
 (0)