Skip to content

Commit 49037f7

Browse files
Merge branch 'MicrosoftDocs:main' into main
2 parents c4922c2 + c5d22a7 commit 49037f7

64 files changed

Lines changed: 749 additions & 233 deletions

File tree

Some content is hidden

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

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ To use the batch transcription REST API:
3636
1. [Get batch transcription results](batch-transcription-get.md) - Check transcription status and retrieve transcription results asynchronously.
3737

3838
> [!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).
39+
> Batch transcription jobs are scheduled on a best-effort basis. At peak 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).
4040
4141
## Next steps
4242

articles/aks/azure-cni-overlay.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -169,7 +169,7 @@ The `--pod-cidr` parameter is required when upgrading from legacy CNI because th
169169

170170
[!INCLUDE [preview features callout](includes/preview/preview-callout.md)]
171171

172-
You must register the `Microsoft.ContainerService` `AzureOverlayDualStackPreview` feature flag.
172+
You must have the latest aks-preview Azure CLI extension installed and register the `Microsoft.ContainerService` `AzureOverlayDualStackPreview` feature flag.
173173

174174
Update an existing Kubenet cluster to use Azure CNI Overlay using the [`az aks update`][az-aks-update] command.
175175

articles/azure-arc/system-center-virtual-machine-manager/disaster-recovery.md

Lines changed: 11 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Recover from accidental deletion of resource bridge VM
33
description: Learn how to perform recovery operations for the Azure Arc resource bridge VM in Azure Arc-enabled System Center Virtual Machine Manager disaster scenarios.
44
ms.topic: how-to
55
ms.custom:
6-
ms.date: 11/15/2023
6+
ms.date: 11/29/2023
77
ms.services: azure-arc
88
ms.subservice: azure-arc-scvmm
99
author: PriskeyJeronika-MS
@@ -13,12 +13,16 @@ manager: jsuri
1313

1414
# Recover from accidental deletion of resource bridge virtual machine
1515

16-
In this article, you'll learn how to recover the Azure Arc resource bridge connection into a working state in disaster scenarios such as accidental deletion. In such cases, the connection between on-premises infrastructure and Azure is lost and any operations performed through Arc will fail.
16+
In this article, you learn how to recover the Azure Arc resource bridge connection into a working state in disaster scenarios such as accidental deletion. In such cases, the connection between on-premises infrastructure and Azure is lost and any operations performed through Arc will fail.
1717

1818
## Recover the Arc resource bridge in case of virtual machine deletion
1919

2020
To recover from Arc resource bridge VM deletion, you need to deploy a new resource bridge with the same resource ID as the current resource bridge using the following steps.
2121

22+
>[!Note]
23+
> This note is applicable only if you're performing this recovery operation to upgrade your Arc resource bridge.<br><br>
24+
> If you have VMs that are still in the older version, i.e., have *Enabled (Deprecated)* set under the *Virtual hardware operations* column in the Virtual Machines inventory of your SCVMM server in Azure, switch them to the new version by following the steps in [this article](./switch-to-the-new-version-scvmm.md#switch-to-the-new-version-existing-customer) before proceeding with the steps for resource bridge recovery.
25+
2226
1. Copy the Azure region and resource IDs of the Arc resource bridge, custom location, and SCVMM Azure resources.
2327

2428
2. Find and delete the old Arc resource bridge resource under the [Resource Bridges tab from the Azure Arc center](https://ms.portal.azure.com/#view/Microsoft_Azure_HybridCompute/AzureArcCenterBlade/~/resourceBridges).
@@ -40,19 +44,19 @@ To recover from Arc resource bridge VM deletion, you need to deploy a new resour
4044
$vmmserverName= <SCVMM-name-in-azure>
4145
```
4246
43-
4. [Run the onboarding script](/azure/azure-arc/system-center-virtual-machine-manager/quickstart-connect-system-center-virtual-machine-manager-to-arc#download-the-onboarding-script) again with the `--force` parameter.
47+
4. [Run the onboarding script](/azure/azure-arc/system-center-virtual-machine-manager/quickstart-connect-system-center-virtual-machine-manager-to-arc#download-the-onboarding-script) again with the `-Force` parameter.
4448
4549
``` powershell-interactive
46-
./resource-bridge-onboarding-script.ps1 --force
50+
./resource-bridge-onboarding-script.ps1 -Force
4751
```
4852
4953
5. [Provide the inputs](/azure/azure-arc/system-center-virtual-machine-manager/quickstart-connect-system-center-virtual-machine-manager-to-arc#script-runtime) as prompted.
5054
5155
6. In the same machine, run the following scripts, as applicable:
52-
- [Download the script](https://download.microsoft.com/download/6/b/4/6b4a5009-fed8-46c2-b22b-b24a4d0a06e3/arcvmm-appliance-dr.ps1) if you are running the script from a Windows machine
53-
- [Download the script](https://download.microsoft.com/download/0/5/c/05c2bcb8-87f8-4ead-9757-a87a0759071c/arcvmm-appliance-dr.sh) if you are running the script from a Linux machine
56+
- [Download the script](https://download.microsoft.com/download/6/b/4/6b4a5009-fed8-46c2-b22b-b24a4d0a06e3/arcvmm-appliance-dr.ps1) if you're running the script from a Windows machine
57+
- [Download the script](https://download.microsoft.com/download/0/5/c/05c2bcb8-87f8-4ead-9757-a87a0759071c/arcvmm-appliance-dr.sh) if you're running the script from a Linux machine
5458
55-
7. Once the script is run successfully, the old Resource Bridge will be recovered and the connection is re-established to the existing Azure-enabled SCVMM resources.
59+
7. Once the script is run successfully, the old Resource Bridge is recovered and the connection is re-established to the existing Azure-enabled SCVMM resources.
5660
5761
## Next steps
5862

articles/azure-arc/system-center-virtual-machine-manager/install-arc-agents-using-script.md

Lines changed: 17 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Install Arc agent using a script for SCVMM VMs
33
description: Learn how to enable guest management using a script for Arc enabled SCVMM VMs.
44
ms.topic: how-to
5-
ms.date: 11/15/2023
5+
ms.date: 11/29/2023
66
ms.service: azure-arc
77
author: PriskeyJeronika-MS
88
ms.author: v-gjeronika
@@ -15,7 +15,7 @@ ms.subservice: azure-arc-scvmm
1515

1616
# Install Arc agents using a script
1717

18-
In this article, you'll learn how to install Arc agents on Azure-enabled SCVMM VMs using a script.
18+
In this article, you learn how to install Arc agents on Azure-enabled SCVMM VMs using a script.
1919

2020
## Prerequisites
2121

@@ -29,22 +29,30 @@ Ensure the following before you install Arc agents using a script for SCVMM VMs:
2929
- Is running a [supported operating system](/azure/azure-arc/servers/prerequisites#supported-operating-systems).
3030
- Is able to connect through the firewall to communicate over the Internet and [these URLs](/azure/azure-arc/servers/network-requirements?tabs=azure-cloud#urls) aren't blocked.
3131
- Has Azure CLI [installed](https://learn.microsoft.com/cli/azure/install-azure-cli).
32-
- Has the Arc agent installation script downloaded from [here](https://download.microsoft.com/download/7/1/6/7164490e-6d8c-450c-8511-f8191f6ec110/arcscvmm-enable-guest-management.ps1).
32+
- Has the Arc agent installation script downloaded from [here](https://download.microsoft.com/download/7/1/6/7164490e-6d8c-450c-8511-f8191f6ec110/arcscvmm-enable-guest-management.ps1) for a Windows VM or from [here](https://download.microsoft.com/download/0/9/b/09bd9ef4-a7af-49e5-ad5f-9e8f85fae75b/arcscvmm-enable-guest-management.sh) for a Linux VM.
3333

3434
>[!NOTE]
3535
>- If you're using a Linux VM, the account must not prompt for login on sudo commands. To override the prompt, from a terminal, run `sudo visudo`, and `add <username> ALL=(ALL) NOPASSWD:ALL` at the end of the file. Ensure you replace `<username>`.
3636
>- If your VM template has these changes incorporated, you won't need to do this for the VM created from that template.
3737
3838
## Steps to install Arc agents using a script
3939

40-
1. Log in to the target VM as an administrator.
40+
1. Sign in to the target VM as an administrator.
4141
2. Run the Azure CLI with the `az` command from either Windows Command Prompt or PowerShell.
42-
3. Log in to your Azure account in Azure CLI using `az login --use-device-code`
43-
4. Run the downloaded script *arcscvmm-enable-guest-management.ps1*. The `vmmServerId` parameter should denote your VMM Server’s ARM ID.
42+
3. Sign in to your Azure account in Azure CLI using `az login --use-device-code`
43+
4. Run the downloaded script *arcscvmm-enable-guest-management.ps1* or *arcscvmm-enable-guest-management.sh*, as applicable, using the following commands. The `vmmServerId` parameter should denote your VMM Server’s ARM ID.
4444

45-
```azurecli
46-
./arcscvmm-enable-guest-management.ps1 -<vmmServerId> '/subscriptions/<subscriptionId>/resourceGroups/<rgName>/providers/Microsoft.ScVmm/vmmServers/<vmmServerName>
47-
```
45+
**For a Windows VM:**
46+
47+
```azurecli
48+
./arcscvmm-enable-guest-management.ps1 -<vmmServerId> '/subscriptions/<subscriptionId>/resourceGroups/<rgName>/providers/Microsoft.ScVmm/vmmServers/<vmmServerName>
49+
```
50+
51+
**For a Linux VM:**
52+
53+
```azurecli
54+
./arcscvmm-enable-guest-management.sh -<vmmServerId> '/subscriptions/<subscriptionId>/resourceGroups/<rgName>/providers/Microsoft.ScVmm/vmmServers/<vmmServerName>
55+
```
4856
4957
## Next steps
5058
1.15 MB
Loading

articles/azure-arc/system-center-virtual-machine-manager/switch-to-the-new-version-scvmm.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ author: PriskeyJeronika-MS
77
ms.author: v-gjeronika
88
manager: jsuri
99
ms.topic: how-to
10-
ms.date: 11/15/2023
10+
ms.date: 11/29/2023
1111
keywords: "VMM, Arc, Azure"
1212

1313
#Customer intent: As a VI admin, I want to switch to the new version of Arc-enabled SCVMM and leverage the associated capabilities
@@ -28,7 +28,7 @@ If you've onboarded to Arc-enabled SCVMM before September 22, 2023, for VMs that
2828
> If you had enabled guest management on any of the VMs, [disconnect](/azure/azure-arc/servers/manage-agent?tabs=windows#step-2-disconnect-the-server-from-azure-arc) and [uninstall agents](/azure/azure-arc/servers/manage-agent?tabs=windows#step-3a-uninstall-the-windows-agent).
2929
3030
1. From your browser, go to the SCVMM management servers blade on [Azure Arc Center](https://ms.portal.azure.com/#view/Microsoft_Azure_HybridCompute/AzureArcCenterBlade/~/overview) and select the SCVMM management server resource.
31-
2. Select all the virtual machines that are Azure enabled with the older version.
31+
2. Select all the virtual machines that are Azure enabled with the older version. The virtual machines in the older version will have *Enabled (Deprecated)* set under the Virtual hardware management column.
3232
3. Select **Remove from Azure**.
3333
:::image type="Virtual Machines" source="media/switch-to-the-new-version-scvmm/virtual-machines.png" alt-text="Screenshot of virtual machines.":::
3434
4. After successful removal from Azure, enable the same resources again in Azure.

articles/azure-functions/TOC.yml

Lines changed: 25 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -399,7 +399,31 @@
399399
- name: PowerShell
400400
href: functions-reference-powershell.md
401401
- name: Python
402-
href: functions-reference-python.md
402+
items:
403+
- name: Developer reference guide
404+
displayName: python
405+
href: functions-reference-python.md
406+
- name: Programming models
407+
displayName: python
408+
href: functions-reference-python.md#programming-model
409+
- name: Python worker extensions
410+
href: develop-python-worker-extensions.md
411+
- name: Scale and performance recommendations
412+
displayName: python
413+
href: python-scale-performance-reference.md
414+
- name: Troubleshooting
415+
items:
416+
- name: General troubleshooting
417+
displayName: python
418+
href: recover-python-functions.md
419+
- name: Memory profiling
420+
displayName: python
421+
href: python-memory-profiler-reference.md
422+
- name: Python library API reference for Functions
423+
href: /python/api/azure-functions/azure.functions
424+
- name: Samples
425+
displayName: python
426+
href: /samples/browse/?products=azure-functions&languages=python
403427
- name: How-to guides
404428
items:
405429
- name: Develop

articles/azure-functions/functions-bindings-dapr-input-secret.md

Lines changed: 55 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -68,8 +68,32 @@ public void run(
6868

6969
::: zone pivot="programming-language-javascript"
7070

71-
> [!NOTE]
72-
> The [Node.js v4 model for Azure Functions](functions-reference-node.md?pivots=nodejs-model-v4) isn't currently available for use with the Dapr extension during the preview.
71+
# [Node.js v4](#tab/v4)
72+
73+
In the following example, the Dapr secret input binding is paired with a Dapr invoke trigger, which is registered by the `app` object:
74+
75+
```javascript
76+
const { app, trigger } = require('@azure/functions');
77+
78+
app.generic('RetrieveSecret', {
79+
trigger: trigger.generic({
80+
type: 'daprServiceInvocationTrigger',
81+
name: "payload"
82+
}),
83+
extraInputs: [daprSecretInput],
84+
handler: async (request, context) => {
85+
context.log("Node function processed a RetrieveSecret request from the Dapr Runtime.");
86+
const daprSecretInputValue = context.extraInputs.get(daprSecretInput);
87+
88+
// print the fetched secret value
89+
for (var key in daprSecretInputValue) {
90+
context.log(`Stored secret: Key=${key}, Value=${daprSecretInputValue[key]}`);
91+
}
92+
}
93+
});
94+
```
95+
96+
# [Node.js v3](#tab/v3)
7397

7498
The following examples show Dapr triggers in a _function.json_ file and JavaScript code that uses those bindings.
7599

@@ -105,6 +129,8 @@ module.exports = async function (context) {
105129
};
106130
```
107131

132+
---
133+
108134
::: zone-end
109135

110136
::: zone pivot="programming-language-powershell"
@@ -269,7 +295,33 @@ The `DaprSecretInput` annotation allows you to have your function access a secre
269295

270296
::: zone-end
271297

272-
::: zone pivot="programming-language-javascript, programming-language-powershell"
298+
::: zone pivot="programming-language-javascript"
299+
300+
# [Node.js v4](#tab/v4)
301+
302+
The following table explains the binding configuration properties that you set in the code.
303+
304+
|Property | Description |
305+
|-----------------------|-------------|
306+
|**key** | The secret key value. |
307+
|**secretStoreName** | Name of the secret store as defined in the _local-secret-store.yaml_ component file. |
308+
|**metadata** | The metadata namespace. |
309+
310+
# [Node.js v3](#tab/v3)
311+
312+
The following table explains the binding configuration properties that you set in the function.json file.
313+
314+
|function.json property | Description |
315+
|-----------------------|-------------|
316+
|**key** | The secret key value. |
317+
|**secretStoreName** | Name of the secret store as defined in the _local-secret-store.yaml_ component file. |
318+
|**metadata** | The metadata namespace. |
319+
320+
---
321+
322+
::: zone-end
323+
324+
::: zone pivot="programming-language-powershell"
273325

274326
The following table explains the binding configuration properties that you set in the function.json file.
275327

articles/azure-functions/functions-bindings-dapr-input-state.md

Lines changed: 44 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -70,8 +70,35 @@ public String run(
7070

7171
::: zone pivot="programming-language-javascript"
7272

73-
> [!NOTE]
74-
> The [Node.js v4 model for Azure Functions](functions-reference-node.md?pivots=nodejs-model-v4) isn't currently available for use with the Dapr extension during the preview.
73+
# [Node.js v4](#tab/v4)
74+
75+
In the following example, the Dapr invoke input binding is added as an `extraInput` and paired with an HTTP trigger, which is registered by the `app` object:
76+
77+
```javascript
78+
const { app, trigger } = require('@azure/functions');
79+
80+
app.generic('StateInputBinding', {
81+
trigger: trigger.generic({
82+
type: 'httpTrigger',
83+
authLevel: 'anonymous',
84+
methods: ['GET'],
85+
route: "state/{key}",
86+
name: "req"
87+
}),
88+
extraInputs: [daprStateInput],
89+
handler: async (request, context) => {
90+
context.log("Node HTTP trigger function processed a request.");
91+
92+
const daprStateInputValue = context.extraInputs.get(daprStateInput);
93+
// print the fetched state value
94+
context.log(daprStateInputValue);
95+
96+
return daprStateInputValue;
97+
}
98+
});
99+
```
100+
101+
# [Node.js v3](#tab/v3)
75102

76103
The following examples show Dapr triggers in a _function.json_ file and JavaScript code that uses those bindings.
77104

@@ -101,6 +128,8 @@ module.exports = async function (context, req) {
101128
};
102129
```
103130

131+
---
132+
104133
::: zone-end
105134

106135
::: zone pivot="programming-language-powershell"
@@ -254,13 +283,26 @@ The `DaprStateInput` annotation allows you to read Dapr state into your function
254283

255284
::: zone pivot="programming-language-javascript"
256285

286+
# [Node.js v4](#tab/v4)
287+
288+
The following table explains the binding configuration properties that you set in the code.
289+
290+
|Property | Description |
291+
|-----------------------|-------------|
292+
|**stateStore** | The name of the state store. |
293+
|**key** | The name of the key to retrieve from the specified state store. |
294+
295+
# [Node.js v3](#tab/v3)
296+
257297
The following table explains the binding configuration properties that you set in the function.json file.
258298

259299
|function.json property | Description |
260300
|-----------------------|-------------|
261301
|**stateStore** | The name of the state store. |
262302
|**key** | The name of the key to retrieve from the specified state store. |
263303

304+
---
305+
264306
::: zone-end
265307

266308
::: zone pivot="programming-language-powershell"

0 commit comments

Comments
 (0)