Skip to content

Commit fad1fd2

Browse files
committed
Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into patricka-remove-marketplace-ref
2 parents a33beec + 79440a1 commit fad1fd2

26 files changed

+208
-127
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/automation/learn/automation-tutorial-runbook-textual.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -314,7 +314,7 @@ You can use the `ForEach -Parallel` construct to process commands for each item
314314
|VMs|Enter the names of the virtual machines using the following syntax: `["VM1","VM2","VM3"]`|
315315
|Action|Enter `stop` or `start`.|
316316
317-
1. Navigate to your list of virtual machines and refresh the page every few seconds. Observe that the action for each VM happens in parallel. Without the `-Parallel` keyword, the actions would have performed sequentially. While the VMs will start sequentially, each VM may reach the **Running** phase at slightly different times based on the characteristics of each VM.
317+
1. Navigate to your list of virtual machines and refresh the page every few seconds. Observe that the action for each VM happens in parallel. Without the `-Parallel` keyword, the actions would have performed sequentially. While the VMs will start in parallel, each VM may reach the **Running** phase at slightly different times based on the characteristics of each VM.
318318
319319
## Clean up resources
320320

articles/automation/manage-sql-server-in-automation.md

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -51,10 +51,12 @@ To allow access from the Automation system managed identity to the Azure SQL dat
5151
1. Go to [Azure portal](https://portal.azure.com) home page and select **SQL servers**.
5252
1. In the **SQL server** page, under **Settings**, select **SQL Databases**.
5353
1. Select your database to go to the SQL database page and select **Query editor (preview)** and execute the following two queries:
54-
- CREATE USER "AutomationAccount" FROM EXTERNAL PROVIDER WITH OBJECT_ID= `ObjectID`
55-
- EXEC sp_addrolemember `db_owner`, "AutomationAccount"
56-
- Automation account - replace with your Automation account's name
57-
- Object ID - replace with object (principal) ID for your system managed identity principal from step 1.
54+
```sql
55+
# AutomationAccount - replace with your Automation account's name
56+
# ObjectID - replace with object (principal) ID for your system managed identity principal from step 1.
57+
CREATE USER "AutomationAccount" FROM EXTERNAL PROVIDER WITH OBJECT_ID = `ObjectID`
58+
EXEC sp_addrolemember `db_owner`, "AutomationAccount"
59+
```
5860

5961
## Sample code
6062

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/azure-maps/routing-coverage.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -479,7 +479,6 @@ The Azure Maps Routing service (preview) contains different levels of geographic
479479
| Kazakhstan | Good | |||
480480
| Kenya | Good ||||
481481
| Kiribati | Major Roads Only | || |
482-
| Korea | Good || | |
483482
| Kosovo | Good | | | |
484483
| Kuwait | Good ||||
485484
| Kyrgyzstan | Major Roads Only | || |

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/hierarchical-partition-keys.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -671,7 +671,7 @@ items = list(container.query_items(
671671

672672
## Limitations and known issues
673673

674-
- Working with containers that use hierarchical partition keys is supported only in the .NET v3 SDK, in the Java v4 SDK, and in the preview version of the JavaScript SDK. You must use a supported SDK to create new containers that have hierarchical partition keys and to perform CRUD or query operations on the data. Support for other SDKs, including Python, isn't available currently.
674+
- Working with containers that use hierarchical partition keys is supported only in the .NET v3 SDK, in the Java v4 SDK, in the Python SDK, and in the preview version of the JavaScript SDK. You must use a supported SDK to create new containers that have hierarchical partition keys and to perform CRUD or query operations on the data. Support for other SDKs, including Python, isn't available currently.
675675
- There are limitations with various Azure Cosmos DB connectors (for example, with Azure Data Factory).
676676
- You can specify hierarchical partition keys only up to three layers in depth.
677677
- Hierarchical partition keys can currently be enabled only on new containers. You must set partition key paths at the time of container creation, and you can't change them later. To use hierarchical partitions on existing containers, create a new container with the hierarchical partition keys set and move the data by using [container copy jobs](container-copy.md).

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/monitor-resource-logs.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -35,6 +35,11 @@ Platform metrics and the Activity logs are collected automatically, whereas you
3535
- Alternatively, you can [try Azure Cosmos DB free](try-free.md) before you commit.
3636
- An existing Azure Monitor Log Analytics workspace.
3737

38+
> [!WARNING]
39+
> If you need to delete a resource, rename, or move a resource, or migrate it across resource groups or subscriptions, first delete its diagnostic settings. Otherwise, if you recreate this resource, the diagnostic settings for the deleted resource could be included with the new resource, depending on the resource configuration for each resource. If the diagnostics settings are included with the new resource, this resumes the collection of resource logs as defined in the diagnostic setting and sends the applicable metric and log data to the previously configured destination.
40+
>
41+
> Also, it's a good practice to delete the diagnostic settings for a resource you're going to delete and don't plan on using again to keep your environment clean.
42+
3843
## Create diagnostic settings
3944

4045
Here, we walk through the process of creating diagnostic settings for your account.

0 commit comments

Comments
 (0)