Skip to content

Commit 93dbf26

Browse files
author
ecfan
committed
Calc work
1 parent e728fef commit 93dbf26

File tree

1 file changed

+25
-19
lines changed

1 file changed

+25
-19
lines changed

articles/logic-apps/set-up-standard-workflows-hybrid-deployment-requirements.md

Lines changed: 25 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -49,45 +49,51 @@ This how-to guide shows how to set up the necessary on-premises resources in you
4949

5050
## How billing works
5151

52-
The hybrid option uses a billing model where you pay only for what you need and can scale resources for dynamic workloads without having to buy for peak usage.
53-
54-
You're responsible for the following items:
52+
The hybrid option uses a billing model where you pay only for what you need and can scale resources for dynamic workloads without having to buy for peak usage. You're responsible for the following items:
5553

5654
- Your Azure Arc-enabled Kubernetes infrastructure
5755

5856
- Your SQL Server license
5957

60-
- vCPU usage billed at a rate of $0.18 USD per hour to support Standard logic app workloads
58+
- Billing charges for vCPU usage to support Standard logic app workloads
59+
60+
For more information, see the following sections:
61+
62+
- [vCPU usage calculation](#vcpu-usage-calculation)
63+
- [Billing charge calculation](#billing-charge-calculation)
6164

62-
For more information, see [Calculation for vCPU usage](#vcpu-usage-calculation).
65+
- Billing charges for any [managed (shared) connector operations](../connectors/managed.md), such as Microsoft Teams or Microsoft Office 365, in your logic app workflows.
6366

64-
- Any [managed (shared) connector operations](../connectors/managed.md), such as Microsoft Teams or Microsoft Office 365, follow [Standard pricing](https://azure.microsoft.com/pricing/details/logic-apps/#pricing).
67+
These operation executions follow [Standard pricing](https://azure.microsoft.com/pricing/details/logic-apps/#pricing).
6568

6669
<a name="vcpu-usage-calculation"></a>
6770

6871
### vCPU usage calculation
6972

70-
Your Standard logic app resource uses vCPU and memory allocation and [replica scaling] that affects your billing charge.
73+
The vCPU usage for your Standard logic app affects your billing charges. The following formula calculates the vCPU usage for your logic app:
7174

72-
(create-standard-workflows-hybrid-deployment.md#change-vcpu-and-memory-allocation-in-the-azure-portal)
75+
**vCPU usage** = (**# of allocated vCPUs**) x (**# of replicas**)
7376

74-
By default, your Standard logic app resource uses a specific number of vCPU cores. You can change this number of cores up to the maximum.
75-
Each new instance of a logic app resource revision or version has a maximum of two vCPU cores. By default, each logic app resource uses one vCPU core out of this maximum
77+
| Value | Description |
78+
|-------|-------------|
79+
| **# of allocated vCPUs** | By default, your logic app is allocated a default number of vCPUs. You can [change this vCPU allocation](create-standard-workflows-hybrid-deployment.md#change-vcpu-and-memory-allocation-in-the-azure-portal) anytime after you create your logic app resource. <br><br>**Note**: The extra vCPUs that you allocate come from replica vCPUs. For more information, see the next row. |
80+
| **# of replicas** | A [*replica*](create-standard-workflows-hybrid-deployment.md#change-replica-scaling-in-azure-portal) is a new instance of a logic app resource revision or version that deploys when a workflow trigger event occurs. This number of replicas can vary due to your app's scaling needs at any given time. You can [change the minimum and maximum number of replicas](create-standard-workflows-hybrid-deployment.md#change-replica-scaling-in-azure-portal) that each version or revision can have to meet scaling needs. <br><br>**Note**: Each replica can have two vCPUs. The extra vCPUs that you allocate to your logic app come from replica vCPUs. |
7681

77-
of the maximum two vCPU cores for each [replica](create-standard-workflows-hybrid-deployment.md#change-replica-scaling-in-azure-portal). You can increase this usage to the maximum two vCPU cores.
82+
<a name="billing-charge-calculation"></a>
7883

79-
Based on the allocated value multiplied by the number of replicas, the VCPU usage of the app will be calculated.
84+
### Billing charge calculation
8085

81-
The vCPU usage per hour is calculated based on the following formula:
86+
The following formula calculates your billing charge per hour, which is based on vCPU usage and the rate of $0.18 USD per hour:
8287

83-
(# of allocated vCPU cores) * (# of replicas) * (billing rate) * (# of hours)
88+
**Charge per hour** = (**vCPU usage**) x (**rate per hour**)
8489

85-
For example, if you change the replica scaling, the following table shows some example billed calculations:
90+
For example, the following table shows some example billing charge calculations:
8691

87-
| # of vCPUs | # of replicas | vCPU usage | Billing rate | Billing charge per hour |
88-
|------------|---------------|------------|--------------|-------------------------|
89-
| 0.5 | 2 | 1 | $0.18 | $0.18 |
90-
| 0.5 | 1 | 0.5 | $0.18 | $0.09 |
92+
| # of allocated vCPUs | # of replicas | vCPU usage | $USD rate per hour | Charge per hour |
93+
|----------------------|---------------|------------|--------------------|-----------------|
94+
| 1 | 1 | (1 x 1) = 1 | $0.18 | (1 x $0.18) = **$0.18** |
95+
| 0.5 | 2 | (0.5 x 2) = 1 | $0.18 | (1 x $0.18) = **$0.18** |
96+
| 0.5 | 1 | (0.5 x 1) = 0.5 | $0.18 | (0.5 x $0.18) = **$0.09** |
9197

9298
## Limitations
9399

0 commit comments

Comments
 (0)