You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-functions/dotnet-isolated-in-process-differences.md
+17-17Lines changed: 17 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ recommendations: false
9
9
#Customer intent: As a developer, I need to understand the differences between running in-process and running in an isolated worker process so that I can choose the best process model for my functions.
10
10
---
11
11
12
-
# Differences between in-process and isolated worker process .NET Azure Functions
12
+
# Differences between isolated worker model and in-process model .NET Azure Functions
13
13
14
14
There are two process models for .NET functions:
15
15
@@ -21,23 +21,23 @@ This article describes the current state of the functional and behavioral differ
21
21
22
22
Use the following table to compare feature and functional differences between the two models:
23
23
24
-
| Feature/behavior |In-process<sup>3</sup>| Isolated worker process |
24
+
| Feature/behavior |Isolated worker process |In-process<sup>3</sup> |
25
25
| ---- | ---- | ---- |
26
-
|[Supported .NET versions](#supported-versions)| Long Term Support (LTS) versions<sup>6</sup>| Long Term Support (LTS) versions<sup>6</sup>,<br/>Standard Term Support (STS) versions,<br/>.NET Framework|
| Durable Functions |[Supported](durable/durable-functions-overview.md)|[Supported](durable/durable-functions-isolated-create-first-csharp.md?pivots=code-editor-visualstudio) (Support does not yet include Durable Entities) |
| Output binding interactions | Return values (single output only),<br/>`out` parameters,<br/>`IAsyncCollector`| Return values in an expanded model with:<br/> - single or [multiple outputs](dotnet-isolated-process-guide.md#multiple-output-bindings)<br/> - arrays of outputs|
| Logging |[ILogger] passed to the function<br/>[ILogger<T>] via [dependency injection](functions-dotnet-dependency-injection.md)|[ILogger<T>]/[ILogger] obtained from [FunctionContext](/dotnet/api/microsoft.azure.functions.worker.functioncontext) or via [dependency injection](dotnet-isolated-process-guide.md#dependency-injection)|
|[Supported .NET versions](#supported-versions)| Long Term Support (LTS) versions<sup>6</sup>,<br/>Standard Term Support (STS) versions,<br/>.NET Framework | Long Term Support (LTS) versions<sup>6</sup>|
| Durable Functions |[Supported](durable/durable-functions-isolated-create-first-csharp.md?pivots=code-editor-visualstudio) (Support does not yet include Durable Entities) |[Supported](durable/durable-functions-overview.md)|
| Output binding interactions | Return values in an expanded model with:<br/> - single or [multiple outputs](dotnet-isolated-process-guide.md#multiple-output-bindings)<br/> - arrays of outputs| Return values (single output only),<br/>`out` parameters,<br/>`IAsyncCollector`|
33
+
| Imperative bindings<sup>1</sup> | Not supported - instead [work with SDK types directly](./dotnet-isolated-process-guide.md#register-azure-clients)|[Supported](functions-dotnet-class-library.md#binding-at-runtime)|
34
+
| Dependency injection |[Supported](dotnet-isolated-process-guide.md#dependency-injection) (improved model consistent with .NET ecosystem)|[Supported](functions-dotnet-dependency-injection.md)|
35
+
| Middleware |[Supported](dotnet-isolated-process-guide.md#middleware)| Not supported|
36
+
| Logging |[ILogger<T>]/[ILogger] obtained from [FunctionContext](/dotnet/api/microsoft.azure.functions.worker.functioncontext) or via [dependency injection](dotnet-isolated-process-guide.md#dependency-injection)|[ILogger] passed to the function<br/>[ILogger<T>] via [dependency injection](functions-dotnet-dependency-injection.md)|
<sup>1</sup> When you need to interact with a service using parameters determined at runtime, using the corresponding service SDKs directly is recommended over using imperative bindings. The SDKs are less verbose, cover more scenarios, and have advantages for error handling and debugging purposes. This recommendation applies to both models.
Copy file name to clipboardExpand all lines: articles/azure-portal/azure-portal-add-remove-sort-favorites.md
+9-7Lines changed: 9 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,25 +1,27 @@
1
1
---
2
2
title: Manage favorites in Azure portal
3
-
description: Learn how to add or remove services from the favorites list.
4
-
ms.date: 02/17/2022
3
+
description: Learn how to add or remove services from the Favorites list.
4
+
ms.date: 09/27/2023
5
5
ms.topic: how-to
6
6
---
7
7
8
8
# Manage favorites
9
9
10
-
Add or remove items from your **Favorites** list in the Azure portal so that you can quickly go to the services you use most often. We've already added some common services to your **Favorites** list, but you may want to customize it. You're the only one who sees the changes you make to **Favorites**.
10
+
The **Favorites** list in the Azure portal lets you quickly go to the services you use most often. We've already added some common services to your **Favorites** list, but you may want to customize it by adding or removing items. You're the only one who sees the changes you make to **Favorites**.
11
+
12
+
You can view your **Favorites** list in the Azure portal menu, or from the **Favorites** section within **All services**.
11
13
12
14
## Add a favorite service
13
15
14
-
Items that are listed under **Favorites** are selected from **All services**. Hover over a service name to display information and resources related to the service. A filled star icon  next to the service name indicates that the item appears on the **Favorites** list. Select the star icon to add a service to the **Favorites** list.
16
+
Items that are listed under **Favorites** are selected from **All services**. Within **All services**, you can hover over a service name to display information and resources related to the service. A filled star icon  next to the service name indicates that the item appears in the **Favorites** list. If the star icon isn't filled in for a service, select the star icon to add it to your**Favorites** list.
15
17
16
18
In this example, we'll add **Cost Management + Billing** to the **Favorites** list.
17
19
18
20
1. Select **All services** from the Azure portal menu.
19
21
20
22
:::image type="content" source="media/azure-portal-add-remove-sort-favorites/azure-portal-favorites-new-all-services.png" alt-text="Screenshot showing All services in the Azure portal menu.":::
21
23
22
-
1. Enter the word "cost" in the search field. Services that have "cost" in the title or that have "cost" as a keyword are shown.
24
+
1. Enter the word "cost" in the **Filter services**field near the top of the **All services** page. Services that have "cost" in the title or that have "cost" as a keyword are shown.
23
25
24
26
:::image type="content" source="media/azure-portal-add-remove-sort-favorites/azure-portal-favorites-find-service.png" alt-text="Screenshot showing a search in All services in the Azure portal.":::
25
27
@@ -31,9 +33,9 @@ In this example, we'll add **Cost Management + Billing** to the **Favorites** li
31
33
32
34
## Remove an item from Favorites
33
35
34
-
You can now remove an item directly from the **Favorites** list.
36
+
You can remove items directly from the **Favorites** list.
35
37
36
-
1. In the **Favorites** section of the portal menu, hover over the name of the service you want to remove.
38
+
1. In the **Favorites** section of the portal menu, or within the **Favorites** section of **All services**, hover over the name of the service you want to remove.
37
39
38
40
:::image type="content" source="media/azure-portal-add-remove-sort-favorites/azure-portal-favorites-remove.png" alt-text="Screenshot showing how to remove a service from Favorites in the Azure portal.":::
Copy file name to clipboardExpand all lines: articles/reliability/reliability-image-builder.md
+49-5Lines changed: 49 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ ms.date: 08/22/2023
12
12
13
13
# Reliability in Azure Image Builder (AIB)
14
14
15
-
This article describes reliability support in Azure Image Builder. Azure Image Builder doesn't currently support availability zones at this time, however it does support [cross-regional resiliency with disaster recovery](#disaster-recovery-cross-region-failover).
15
+
This article contains [specific reliability recommendations for Image Builder](#reliability-recommendations) and [cross-region disaster recovery and business continuity](#cross-region-disaster-recovery-and-business-continuity).
16
16
17
17
18
18
Azure Image Builder (AIB) is a regional service with a cluster that serves single regions. The AIB regional setup keeps data and resources within the regional boundary. AIB as a service doesn't do fail over for cluster and SQL database in region down scenarios.
@@ -21,14 +21,58 @@ Azure Image Builder (AIB) is a regional service with a cluster that serves singl
21
21
For an architectural overview of reliability in Azure, see [Azure reliability](/azure/architecture/framework/resiliency/overview).
22
22
23
23
24
-
## Disaster recovery: cross-region failover
24
+
>[!NOTE]
25
+
> Azure Image Builder doesn't support [availability zones](./availability-zones-overview.md).
25
26
26
-
If a region-wide disaster occurs, Azure can provide protection from regional or large geography disasters with disaster recovery by making use of another region. For more information on Azure disaster recovery architecture, see [Azure to Azure disaster recovery architecture](../site-recovery/azure-to-azure-architecture.md).
When building your image templates, use source images that support generation 2 VMs. Generation 2 VMs support key features that aren’t supported in generation 1 VMs such as:
45
+
46
+
- Increased memory
47
+
- Support for disks greater than 2TB
48
+
- New UEFI-based boot architecture instead, which can improve boot and installation times
49
+
- Intel Software Guard Extensions (Intel SGX)
50
+
- Virtualized persistent memory (vPMEM)
51
+
52
+
53
+
For more information on generation 2 VM features and capabilities, see [Generation 2 VMs: Features and capabilities](/azure/virtual-machines/generation-2#features-and-capabilities).
54
+
55
+
### Disaster recovery
56
+
57
+
#### :::image type="icon" source="media/icon-recommendation-low.svg"::: **Replicate image templates to a secondary region**
58
+
59
+
The Azure Image Builder service that's used to deploy Image Templates doesn’t currently support availability zones. Therefore, when building your image templates, you should replicate them to a secondary region, preferably to your primary region’s [paired region](./availability-zones-overview.md#paired-and-unpaired-regions). With a secondary region, you can quickly recover from a region failure and continue to deploy virtual machines from your image templates. For more information, see [Cross-region disaster recovery and business continuity](#cross-region-disaster-recovery-and-business-continuity).
## Cross-region disaster recovery and business continuity
69
+
70
+
[!INCLUDE [introduction to disaster recovery](includes/reliability-disaster-recovery-description-include.md)]
27
71
28
72
To ensure fast and easy recovery for Azure Image Builder (AIB), it's recommended that you run an image template in region pairs or multiple regions when designing your AIB solution. You should also replicate resources from the start when you're setting up your image templates.
29
73
30
74
31
-
### Cross-region disaster recovery in multi-region geography
75
+
### Multi-region geography disaster recovery
32
76
33
77
When a regional disaster occurs, Microsoft is responsible for outage detection, notifications, and support for AIB. However, you're responsible for setting up disaster recovery for the control (service side) and data planes.
34
78
@@ -79,6 +123,6 @@ In regards to your data processing information, refer to the Azure Image Builder
79
123
80
124
## Next steps
81
125
82
-
-[Reliability in Azure](../reliability/overview.md)
126
+
-[Reliability in Azure](overview.md)
83
127
-[Enable Azure VM disaster recovery between availability zones](../site-recovery/azure-to-azure-how-to-enable-zone-to-zone-disaster-recovery.md)
Copy file name to clipboardExpand all lines: includes/functions-bindings-csharp-intro-with-csx.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,6 +8,6 @@ ms.author: glenga
8
8
9
9
A C# function can be created by using one of the following C# modes:
10
10
11
-
*[In-process class library](../articles/azure-functions/functions-dotnet-class-library.md): Compiled C# function that runs in the same process as the Functions runtime.
12
-
*[Isolated worker process class library](../articles/azure-functions/dotnet-isolated-process-guide.md): Compiled C# function that runs in a worker process that's isolated from the runtime. Isolated worker process is required to support C# functions running on LTS and non-LTS versions .NET and the .NET Framework.
11
+
*[Isolated worker model](../articles/azure-functions/dotnet-isolated-process-guide.md): Compiled C# function that runs in a worker process that's isolated from the runtime. Isolated worker process is required to support C# functions running on LTS and non-LTS versions .NET and the .NET Framework.
12
+
*[In-process model](../articles/azure-functions/functions-dotnet-class-library.md): Compiled C# function that runs in the same process as the Functions runtime.
13
13
*[C# script](../articles/azure-functions/functions-reference-csharp.md): Used primarily when you create C# functions in the Azure portal.
Copy file name to clipboardExpand all lines: includes/functions-bindings-csharp-intro.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,5 +8,5 @@ ms.author: glenga
8
8
9
9
A C# function can be created by using one of the following C# modes:
10
10
11
-
*[In-process class library](../articles/azure-functions/functions-dotnet-class-library.md): Compiled C# function that runs in the same process as the Functions runtime. In a variation of this model, Functions can be run using [C# scripting](../articles/azure-functions/functions-reference-csharp.md), which is supported primarily for C# portal editing. Extensions for in-process functions use `Microsoft.Azure.WebJobs.Extensions.*` namespaces.
12
-
*[Isolated worker process class library](../articles/azure-functions/dotnet-isolated-process-guide.md): Compiled C# function that runs in a worker process that's isolated from the runtime. Isolated worker process is required to support C# functions running on LTS and non-LTS versions .NET and the .NET Framework. Extensions for isolated worker process functions use `Microsoft.Azure.Functions.Worker.Extensions.*` namespaces.
11
+
*[Isolated worker model](../articles/azure-functions/dotnet-isolated-process-guide.md): Compiled C# function that runs in a worker process that's isolated from the runtime. Isolated worker process is required to support C# functions running on LTS and non-LTS versions .NET and the .NET Framework. Extensions for isolated worker process functions use `Microsoft.Azure.Functions.Worker.Extensions.*` namespaces.
12
+
*[In-process model](../articles/azure-functions/functions-dotnet-class-library.md): Compiled C# function that runs in the same process as the Functions runtime. In a variation of this model, Functions can be run using [C# scripting](../articles/azure-functions/functions-reference-csharp.md), which is supported primarily for C# portal editing. Extensions for in-process functions use `Microsoft.Azure.WebJobs.Extensions.*` namespaces.
0 commit comments