Skip to content

Commit 9f4fb7b

Browse files
authored
Merge branch 'MicrosoftDocs:main' into minor-uuf-fixes
2 parents 04c4e2a + d93784d commit 9f4fb7b

File tree

14 files changed

+130
-84
lines changed

14 files changed

+130
-84
lines changed

articles/advisor/advisor-overview.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Introduction to Azure Advisor
33
description: Use Azure Advisor to optimize your Azure deployments.
44
ms.topic: overview
5-
ms.date: 04/07/2022
5+
ms.date: 07/08/2024
66
---
77

88
# Introduction to Azure Advisor
@@ -22,11 +22,11 @@ You can access Advisor through the [Azure portal](https://aka.ms/azureadvisordas
2222

2323
The Advisor dashboard displays personalized recommendations for all your subscriptions. The recommendations are divided into five categories:
2424

25-
* **Reliability**: To ensure and improve the continuity of your business-critical applications. For more information, see [Advisor Reliability recommendations](advisor-high-availability-recommendations.md).
25+
* **Reliability**: To ensure and improve the continuity of your business-critical applications. For more information, see [Advisor Reliability recommendations](advisor-reference-reliability-recommendations.md).
2626
* **Security**: To detect threats and vulnerabilities that might lead to security breaches. For more information, see [Advisor Security recommendations](advisor-security-recommendations.md).
27-
* **Performance**: To improve the speed of your applications. For more information, see [Advisor Performance recommendations](advisor-performance-recommendations.md).
28-
* **Cost**: To optimize and reduce your overall Azure spending. For more information, see [Advisor Cost recommendations](advisor-cost-recommendations.md).
29-
* **Operational Excellence**: To help you achieve process and workflow efficiency, resource manageability and deployment best practices. For more information, see [Advisor Operational Excellence recommendations](advisor-operational-excellence-recommendations.md).
27+
* **Performance**: To improve the speed of your applications. For more information, see [Advisor Performance recommendations](advisor-reference-performance-recommendations.md).
28+
* **Cost**: To optimize and reduce your overall Azure spending. For more information, see [Advisor Cost recommendations](advisor-reference-cost-recommendations.md).
29+
* **Operational Excellence**: To help you achieve process and workflow efficiency, resource manageability and deployment best practices. For more information, see [Advisor Operational Excellence recommendations](advisor-reference-operational-excellence-recommendations.md).
3030

3131
You can apply filters to display recommendations for specific subscriptions and resource types.
3232

@@ -65,8 +65,8 @@ To learn more about Advisor recommendations, see:
6565

6666
* [Get started with Advisor](advisor-get-started.md)
6767
* [Advisor score](azure-advisor-score.md)
68-
* [Advisor Reliability recommendations](advisor-high-availability-recommendations.md)
68+
* [Advisor Reliability recommendations](advisor-reference-reliability-recommendations.md)
6969
* [Advisor Security recommendations](advisor-security-recommendations.md)
70-
* [Advisor Performance recommendations](advisor-performance-recommendations.md)
71-
* [Advisor Cost recommendations](advisor-cost-recommendations.md)
72-
* [Advisor operational excellence recommendations](advisor-operational-excellence-recommendations.md)
70+
* [Advisor Performance recommendations](advisor-reference-performance-recommendations.md)
71+
* [Advisor Cost recommendations](advisor-reference-cost-recommendations.md)
72+
* [Advisor Operational Excellence recommendations](advisor-reference-operational-excellence-recommendations.md)

articles/azure-functions/functions-bindings-openai-textcompletion-input.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Azure OpenAI text completion input binding for Azure Functions
33
description: Learn how to use the Azure OpenAI text completion input binding to access Azure OpenAI text completion APIs during function execution in Azure Functions.
44
ms.topic: reference
55
ms.custom: build-2024, devx-track-extended-java, devx-track-js, devx-track-python, devx-track-ts
6-
ms.date: 05/23/2024
6+
ms.date: 07/08/2024
77
zone_pivot_groups: programming-languages-set-functions
88
---
99

@@ -41,14 +41,16 @@ This example takes a prompt as input, sends it directly to the completions API,
4141
::: zone-end
4242
::: zone pivot="programming-language-javascript"
4343

44-
[!INCLUDE [functions-examples-not-available-note](../../includes/functions-examples-not-available-note.md)]
44+
This example demonstrates the _templating_ pattern, where the HTTP trigger function takes a `name` parameter and embeds it into a text prompt, which is then sent to the Azure OpenAI completions API by the extension. The response to the prompt is returned in the HTTP response.
45+
46+
:::code language="javascript" source="~/functions-openai-extension/samples/textcompletion/javascript/src/functions/whois.js" :::
4547

4648
::: zone-end
4749
::: zone pivot="programming-language-typescript"
4850

4951
This example demonstrates the _templating_ pattern, where the HTTP trigger function takes a `name` parameter and embeds it into a text prompt, which is then sent to the Azure OpenAI completions API by the extension. The response to the prompt is returned in the HTTP response.
5052

51-
:::code language="typescript" source="~/functions-openai-extension/samples/textcompletion/nodejs/src/functions/whois.ts" :::
53+
:::code language="typescript" source="~/functions-openai-extension/samples/textcompletion/typescript/src/functions/whois.ts" :::
5254

5355
::: zone-end
5456
::: zone pivot="programming-language-powershell"

articles/communication-services/how-tos/calling-sdk/includes/capabilities/capabilities-web.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -51,6 +51,10 @@ capabilitiesFeature.on('capabilitiesChanged', (capabilitiesChangeInfo) => {
5151
(value.isPresent) ? this.setState({ canRaiseHands: true }) : this.setState({ canRaiseHands: false });
5252
continue;
5353
}
54+
if(key === 'muteOthers' && value.reason != 'FeatureNotSupported') {
55+
(value.isPresent) ? this.setState({ canMuteOthers: true }) : this.setState({ canMuteOthers: false });
56+
continue;
57+
}
5458
if(key === 'reaction' && value.reason != 'FeatureNotSupported') {
5559
(value.isPresent) ? this.setState({ canReact: true }) : this.setState({ canReact: false });
5660
continue;
@@ -74,5 +78,6 @@ capabilitiesFeature.on('capabilitiesChanged', (capabilitiesChangeInfo) => {
7478
- *startLiveCaptions*: Ability to start live captions (beta only)
7579
- *stopLiveCaptions*: Ability to stop live captions (beta only)
7680
- *raiseHand*: Ability to raise hand (beta only)
81+
- *muteOthers*: Ability to soft mute remote participant(s) in the meeting
7782
- *reaction*: Ability to react in the meeting (beta only)
7883
- *viewAttendeeNames*: Ability to view attendee names in the meeting

articles/communication-services/how-tos/calling-sdk/includes/manage-calls/manage-calls-web.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -162,11 +162,11 @@ When incoming audio is muted, the participant client SDK still receives the call
162162

163163
## Mute other participants
164164
> [!NOTE]
165-
> This API is provided as a preview for developers and may change based on feedback that we receive. To use this API please use 'beta' release of Azure Communication Services Calling Web SDK version 1.25.1 or higher.
165+
> To use this API please use Azure Communication Services Calling Web SDK version 1.26.1 or higher.
166166
167-
To mute all other participants or mute a specific participant, you can use the asynchronous APIs `muteAllRemoteParticipants` on the call and `mute` on the remote participant. The `mutedByOthers` event from Call is raised when the local participant has been muted by others.
167+
To mute all other participants or mute a specific participant who are connected to a call, you can use the asynchronous APIs `muteAllRemoteParticipants` on the call and `mute` on the remote participant. The `mutedByOthers` event from Call is raised when the local participant has been muted by others.
168168

169-
*Note: The scenario to mute PSTN (phone number) participants is not supported.*
169+
*Note: The scenarios to mute PSTN (phone number) participants or 1:1 call participants are not supported.*
170170

171171
```js
172172
//mute all participants except yourself

articles/cosmos-db/mongodb/vcore/compatibility.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -286,16 +286,16 @@ Below are the list of operators currently supported on Azure Cosmos DB for Mongo
286286
<tr><td><code>$isArray</code></td><td><img src="media/compatibility/yes-icon.svg" alt="Yes"></td><td><img src="media/compatibility/yes-icon.svg" alt="Yes"></td><td><img src="media/compatibility/yes-icon.svg" alt="Yes"></td></tr>
287287
<tr><td><code>$lastN</code></td><td><img src="media/compatibility/yes-icon.svg" alt="Yes"></td><td><img src="media/compatibility/yes-icon.svg" alt="Yes"></td><td><img src="media/compatibility/yes-icon.svg" alt="Yes"></td></tr>
288288
<tr><td><code>$map</code></td><td><img src="media/compatibility/yes-icon.svg" alt="Yes"></td><td><img src="media/compatibility/yes-icon.svg" alt="Yes"></td><td><img src="media/compatibility/yes-icon.svg" alt="Yes"></td></tr>
289-
<tr><td><code>$maxN</code></td><td></td><td><img src="media/compatibility/no-icon.svg" alt="No"></td><td><img src="media/compatibility/no-icon.svg" alt="No"></td></tr>
290-
<tr><td><code>$minN</code></td><td></td><td><img src="media/compatibility/no-icon.svg" alt="No"></td><td><img src="media/compatibility/no-icon.svg" alt="No"></td></tr>
289+
<tr><td><code>$maxN</code></td><td></td><td><img src="media/compatibility/yes-icon.svg" alt="Yes"></td><td><img src="media/compatibility/yes-icon.svg" alt="Yes"></td></tr>
290+
<tr><td><code>$minN</code></td><td></td><td><img src="media/compatibility/yes-icon.svg" alt="Yes"></td><td><img src="media/compatibility/yes-icon.svg" alt="Yes"></td></tr>
291291
<tr><td><code>$objectToArray</code></td><td><img src="media/compatibility/yes-icon.svg" alt="Yes"></td><td><img src="media/compatibility/yes-icon.svg" alt="Yes"></td><td><img src="media/compatibility/yes-icon.svg" alt="Yes"></td></tr>
292292
<tr><td><code>$range</code></td><td><img src="media/compatibility/yes-icon.svg" alt="Yes"></td><td><img src="media/compatibility/yes-icon.svg" alt="Yes"></td><td><img src="media/compatibility/yes-icon.svg" alt="Yes"></td></tr>
293293
<tr><td><code>$reduce</code></td><td><img src="media/compatibility/yes-icon.svg" alt="Yes"></td><td><img src="media/compatibility/yes-icon.svg" alt="Yes"></td><td><img src="media/compatibility/yes-icon.svg" alt="Yes"></td></tr>
294294
<tr><td><code>$reverseArray</code></td><td><img src="media/compatibility/yes-icon.svg" alt="Yes"></td><td><img src="media/compatibility/yes-icon.svg" alt="Yes"></td><td><img src="media/compatibility/yes-icon.svg" alt="Yes"></td></tr>
295295
<tr><td><code>$size</code></td><td><img src="media/compatibility/yes-icon.svg" alt="Yes"></td><td><img src="media/compatibility/yes-icon.svg" alt="Yes"></td><td><img src="media/compatibility/yes-icon.svg" alt="Yes"></td></tr>
296296
<tr><td><code>$slice</code></td><td><img src="media/compatibility/yes-icon.svg" alt="Yes"></td><td><img src="media/compatibility/yes-icon.svg" alt="Yes"></td><td><img src="media/compatibility/yes-icon.svg" alt="Yes"></td></tr>
297-
<tr><td><code>$sortArray</code></td><td></td><td><img src="media/compatibility/no-icon.svg" alt="No"></td><td><img src="media/compatibility/no-icon.svg" alt="No"></td></tr>
298-
<tr><td><code>$zip</code></td><td><img src="media/compatibility/no-icon.svg" alt="No"></td><td><img src="media/compatibility/no-icon.svg" alt="No"></td><td><img src="media/compatibility/no-icon.svg" alt="No"></td></tr>
297+
<tr><td><code>$sortArray</code></td><td></td><td><img src="media/compatibility/yes-icon.svg" alt="Yes"></td><td><img src="media/compatibility/yes-icon.svg" alt="Yes"></td></tr>
298+
<tr><td><code>$zip</code></td><td><img src="media/compatibility/yes-icon.svg" alt="Yes"></td><td><img src="media/compatibility/yes-icon.svg" alt="Yes"></td><td><img src="media/compatibility/yes-icon.svg" alt="Yes"></td></tr>
299299

300300
<tr><td rowspan="4">Bitwise Operators</td><td><code>$bitAnd</code></td><td><img src="media/compatibility/yes-icon.svg" alt="Yes"></td><td><img src="media/compatibility/yes-icon.svg" alt="Yes"></td><td><img src="media/compatibility/yes-icon.svg" alt="Yes"></td></tr>
301301
<tr><td><code>$bitNot</code></td><td><img src="media/compatibility/yes-icon.svg" alt="Yes"></td><td><img src="media/compatibility/yes-icon.svg" alt="Yes"></td><td><img src="media/compatibility/yes-icon.svg" alt="Yes"></td></tr>

articles/cosmos-db/postgresql/product-updates.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ ms.custom: mvc, references_regions
77
ms.service: cosmos-db
88
ms.subservice: postgresql
99
ms.topic: conceptual
10-
ms.date: 05/28/2024
10+
ms.date: 07/07/2024
1111
---
1212

1313
# Product updates for Azure Cosmos DB for PostgreSQL
@@ -22,6 +22,9 @@ Updates that don’t directly affect the internals of a cluster are rolled out g
2222

2323
Updates that change cluster internals, such as installing a [new minor PostgreSQL version](https://www.postgresql.org/developer/roadmap/), are delivered to existing clusters as part of the next [scheduled maintenance](concepts-maintenance.md) event. Such updates are available immediately to newly created clusters.
2424

25+
### July 2024
26+
* [MD5 hashing is disabled](./reference-limits.md#security) in Azure Cosmos DB for PostgreSQL.
27+
2528
### May 2024
2629
* General availability: [The latest minor PostgreSQL version updates](reference-versions.md#postgresql-versions) (12.19, 13.15, 14.12, 15.7, and 16.3) are now available.
2730
* [The last update for PostgreSQL 11](./reference-versions.md#postgresql-version-11-and-older) was released by community in November 2023.

articles/cosmos-db/postgresql/reference-limits.md

Lines changed: 12 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ author: niklarin
66
ms.service: cosmos-db
77
ms.subservice: postgresql
88
ms.topic: conceptual
9-
ms.date: 01/28/2024
9+
ms.date: 07/07/2024
1010
---
1111

1212
# Azure Cosmos DB for PostgreSQL limits and limitations
@@ -87,12 +87,22 @@ In Azure Cosmos DB for PostgreSQL clusters with [burstable compute](concepts-bur
8787
<a name='azure-active-directory-authentication'></a>
8888

8989
### Microsoft Entra ID authentication
90+
9091
If [Microsoft Entra ID](./concepts-authentication.md#azure-active-directory-authentication-preview) is enabled on an Azure Cosmos DB for PostgreSQL cluster, the following is currently **not supported**:
9192

9293
* PostgreSQL 11, 12, and 13
9394
* Microsoft Entra groups
9495

95-
### Database creation
96+
## Security
97+
98+
MD5 hashing is disabled in Azure Cosmos DB for PostgreSQL and impacts the following areas:
99+
* Native Postgres passwords are hashed using SCRAM-SHA-256 method only.
100+
* [pgcrypto extension](https://www.postgresql.org/docs/current/static/pgcrypto.html): MD5 isn't available as a hashing method.
101+
* [uuid-ossp extension](https://www.postgresql.org/docs/current/static/uuid-ossp.html): MD5 isn't available as a hashing method.
102+
* Built-in Postgres functions. For instance, SELECT md5(‘your_string’);
103+
* Custom functions such as custom functions in PL/pgSQL that use MD5 hashing.
104+
105+
## Database creation
96106

97107
The Azure portal provides credentials to connect to exactly one database per cluster. Creating another database is currently not allowed, and the CREATE DATABASE command fails with an error.
98108

articles/data-factory/control-flow-web-activity.md

Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -160,6 +160,23 @@ Specify the resource uri for which the access token will be requested using the
160160
> [!NOTE]
161161
> If your data factory or Synapse workspace is configured with a git repository, you must store your credentials in Azure Key Vault to use basic or client certificate authentication. The service does not store passwords in git.
162162
163+
### Service principal
164+
165+
Specify the tenant ID, service principal ID, and service principal key, using a secure string for the client secret.
166+
167+
```json
168+
"authentication": {
169+
"type": "ServicePrincipal",
170+
"tenant": "your_tenant_id",
171+
"servicePrincipalId": "your_client_id",
172+
"servicePrincipalKey": {
173+
"type": "SecureString",
174+
"value": "your_client_secret"
175+
},
176+
"resource": "https://management.azure.com/"
177+
}
178+
```
179+
163180
## Request payload schema
164181
When you use the POST/PUT method, the body property represents the payload that is sent to the endpoint. You can pass linked services and datasets as part of the payload. Here is the schema for the payload:
165182

articles/machine-learning/how-to-enable-preview-features.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ ms.topic: how-to
99
ms.reviewer: None
1010
ms.author: larryfr
1111
author: Blackmist
12-
ms.date: 01/29/2024
12+
ms.date: 07/08/2024
1313

1414
---
1515

articles/network-watcher/traffic-analytics-faq.yml

Lines changed: 3 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ metadata:
77
ms.author: halkazwini
88
ms.service: network-watcher
99
ms.topic: faq
10-
ms.date: 04/24/2024
10+
ms.date: 07/08/2024
1111
title: Traffic analytics frequently asked questions (FAQ)
1212
summary: |
1313
This article provides answers to the most frequently asked questions about traffic analytics in Azure Network Watcher.
@@ -127,10 +127,8 @@ sections:
127127
- question: |
128128
How is traffic analytics priced?
129129
answer: |
130-
Traffic analytics is metered. The metering is based on processing of flow log data by the service, and storing the resulting enhanced logs in a Log Analytics workspace.
131-
132-
For example, as per the [Network Watcher pricing](https://azure.microsoft.com/pricing/details/network-watcher/) and [Azure Monitor pricing](https://azure.microsoft.com/pricing/details/monitor/), considering West Central US region, if flow logs data stored in a storage account processed by traffic analytics is 10 GB and enhanced logs ingested in Log Analytics workspace is 1 GB then the applicable charges are:
133-
10 x 2.3$ + 1 x 2.76$ = 25.76$
130+
Traffic analytics is metered. The metering is based on processing of raw flow log data by the service. For more information, see [Network Watcher pricing](https://azure.microsoft.com/pricing/details/network-watcher/).
131+
Enhanced logs ingested in Log Analytics workspace can be retained at no charge for up to first 31 days (or 90 days if Microsoft Sentinel is enabled on the workspace). For more information, see [Azure Monitor pricing](https://azure.microsoft.com/pricing/details/monitor/).
134132
135133
- question: |
136134
How frequently does traffic analytics process data?

0 commit comments

Comments
 (0)