您现在访问的是微软AZURE全球版技术文档网站,若需要访问由世纪互联运营的MICROSOFT AZURE中国区技术文档网站,请访问 https://docs.azure.cn.

Azure 逻辑应用的定价模型Pricing model for Azure Logic Apps

Azure 逻辑应用可帮助你创建和运行可在云中缩放的自动集成工作流。Azure Logic Apps helps you create and run automated integration workflows that can scale in the cloud. 本文介绍 Azure 逻辑应用的计费和定价工作方式。This article describes how billing and pricing work for Azure Logic Apps. 有关定价费率,请参阅逻辑应用定价For pricing rates, see Logic Apps Pricing.

消耗量定价模型Consumption pricing model

对于在公共或 "全局" Azure 逻辑应用服务中运行的新逻辑应用,只需为所使用的内容付费。For new logic apps that run in the public or "global" Azure Logic Apps service, you pay only for what you use. 这些逻辑应用使用基于消耗量的计划和定价模型。These logic apps use a consumption-based plan and pricing model. 在逻辑应用中,每个步骤都是一个操作,Azure 逻辑应用会计量逻辑应用中运行的所有操作。In your logic app, each step is an action, and Azure Logic Apps meters all the actions that run in your logic app.

例如,操作包括:For example, actions include:

  • 触发器,是一种特殊的操作。Triggers, which are special actions. 所有逻辑应用都需要触发器作为第一步。All logic apps require a trigger as the first step.
  • "内置" 或本机操作(如 HTTP、对 AZURE FUNCTIONS 和 API 管理的调用等)"Built-in" or native actions such as HTTP, calls to Azure Functions and API Management, and so on
  • 调用托管连接器,如 Outlook 365、Dropbox 等Calls to managed connectors such as Outlook 365, Dropbox, and so on
  • 控制流步骤,如循环、条件语句等Control flow steps, such as loops, conditional statements, and so on

标准连接器标准连接器价格收费。Standard connectors are charged at the Standard connector price. 通常可用的企业连接器企业连接器价格收费,而公共预览版企业连接器按标准连接器价格收费。Generally available Enterprise connectors are charged at the Enterprise connector price, while public preview Enterprise connectors are charged at the Standard connector price.

详细了解如何对触发器操作进行计费。Learn more about how billing works for triggers and actions.

固定定价模型Fixed pricing model

集成服务环境(ISE)为你创建和运行可访问 Azure 虚拟网络中的资源的逻辑应用提供隔离的方式。An integration service environment (ISE) provides an isolated way for you to create and run logic apps that can access resources in an Azure virtual network. 对于在 ISE 中运行的新逻辑应用,你可以为这些功能支付固定的每月价格For new logic apps that run inside an ISE, you pay a fixed monthly price for these capabilities:

  • 内置触发器和操作Built-in triggers and actions

    在 ISE 中,内置触发器和操作显示 "核心" 标签,并在与逻辑应用相同的 ISE 中运行。Within an ISE, built-in triggers and actions display the Core label and run in the same ISE as your logic apps.

  • 标准连接器和企业连接器(尽可能多的企业连接)Standard connectors and Enterprise connectors (as many Enterprise connections as you want)

    显示ise标签的标准和企业连接器与逻辑应用在同一 ISE 中运行。Standard and Enterprise connectors that display the ISE label run in the same ISE as your logic apps. 不显示 ISE 标签的连接器在全局逻辑应用服务中运行。Connectors that don't display the ISE label run in the global Logic Apps service. 固定的月度定价还适用于在使用在 ISE 中运行的逻辑应用时在全局服务中运行的连接器。Fixed monthly pricing also applies to connectors that run in the global service when you use them with logic apps that run in an ISE.

  • 基于ISE SKU,无需额外付费即可使用集成帐户Integration account usage at no additional cost, based on your ISE SKU:

    每个 ISE SKU 限制为5个集成帐户的总数。Each ISE SKU is limited to 5 total integration accounts. 为实现额外的成本,可以根据 ISE SKU 创建更多的集成帐户:For an additional cost, you can have more integration accounts, based on your ISE SKU:

    • 高级 SKU:最多4个标准帐户。Premium SKU: Up to four more Standard accounts. 无免费帐户或基本帐户。No Free or Basic accounts.

    • 开发人员 SKU:最多4个标准帐户或最多5个标准帐户。Developer SKU: Either up to 4 more Standard accounts, or up to 5 total Standard accounts. 无基本帐户。No Basic accounts.

    有关集成帐户限制的详细信息,请参阅逻辑应用限制和配置For more information about integration account limits, see Logic Apps limits and configuration. 可以在本主题的后面部分了解有关集成帐户层及其定价模型的详细信息。You can learn more about integration account tiers and their pricing model later in this topic.

如果选择高级 ISE SKU,基本单位具有固定容量。If you choose the Premium ISE SKU, the base unit has fixed capacity. 如果需要更多的吞吐量,可以在创建期间或之后添加更多缩放单位If you need more throughput, you can add more scale units, either during creation or afterwards. 开发人员 ISE SKU 不能添加更多缩放单位。The Developer ISE SKU doesn't have the capability to add more scale units. 在 ISE 中运行的逻辑应用不会产生数据保留成本。Logic apps that run in an ISE don't incur data retention costs.

有关定价费率,请参阅逻辑应用定价For pricing rates, see Logic Apps pricing.

连接器Connectors

Azure 逻辑应用连接器通过提供触发器和/或操作来帮助逻辑应用访问云中或本地的应用、服务和系统。Azure Logic Apps connectors help your logic app access apps, services, and systems in the cloud or on premises by providing triggers, actions, or both. 连接器分类为标准或企业。Connectors are classified as either Standard or Enterprise. 有关这些连接器的概述,请参阅适用于 Azure 逻辑应用的连接器For an overview about these connectors, see Connectors for Azure Logic Apps. 如果你想要在逻辑应用中使用的 REST Api 没有预构建的连接器,则可以创建自定义连接器,它们只是围绕这些 rest api 的包装。If no prebuilt connectors are available for the REST APIs that you want to use in your logic apps, you can create custom connectors, which are just wrappers around those REST APIs. 自定义连接器按标准连接器计费。Custom connectors are billed as Standard connectors. 以下各节提供了有关触发器和操作的计费方式的详细信息。The following sections provide more information about how billing for triggers and actions work.

触发器Triggers

触发器是发生特定事件时创建逻辑应用实例的特殊操作。Triggers are special actions that create a logic app instance when a specific event happens. 触发器以不同方式起作用,从而影响逻辑应用的计量方式。Triggers act in different ways, which affect how the logic app is metered. 下面是 Azure 逻辑应用中存在的各种触发器:Here are the various kinds of triggers that exist in Azure Logic Apps:

  • 轮询触发器:此触发器持续检查终结点是否有满足创建逻辑应用实例和启动工作流的条件的消息。Polling trigger: This trigger continually checks an endpoint for messages that satisfy the criteria for creating a logic app instance and starting the workflow. 即使没有创建逻辑应用实例,逻辑应用也会将每个轮询请求计量为执行。Even when no logic app instance gets created, Logic Apps meters each polling request as an execution. 若要指定轮询间隔,请通过逻辑应用程序设计器设置触发器。To specify the polling interval, set up the trigger through the Logic App Designer.

    若要估计更准确的使用成本,请考虑任何给定天可能到达的消息或事件数,而不是仅基于轮询间隔进行计算。To estimate more accurate consumption costs, consider the possible number of messages or events that might arrive on any given day, rather than base your calculations on only the polling interval. 当某个事件或消息满足触发器条件时,许多触发器将立即尝试读取满足条件的任何和所有其他等待事件或消息。When an event or message meets the trigger criteria, many triggers immediately try to read any and all other waiting events or messages that meet the criteria. 此行为意味着,即使你选择较长的轮询间隔,触发器也基于符合启动工作流条件的等待事件或消息的数量进行触发。This behavior means that even when you select a longer polling interval, the trigger fires based on the number of waiting events or messages that qualify for starting workflows. 遵循此行为的触发器包括 Azure 服务总线和 Azure 事件中心。Triggers that follow this behavior include Azure Service Bus and Azure Event Hub.

    因此,例如,假设你设置了一个每天检查终结点的触发器。So, for example, suppose you set up trigger that checks an endpoint every day. 当触发器检查终结点并找到 15 个满足条件的事件时,触发器触发并运行相应工作流 15 次。When the trigger checks the endpoint and finds 15 events that meet the criteria, the trigger fires and runs the corresponding workflow 15 times. 逻辑应用会计量这 15 个工作流执行的所有操作,包括触发器请求。Logic Apps meters all the actions that those 15 workflows perform, including the trigger requests. 若要计算潜在成本,请尝试使用 Azure 定价计算器To calculate your potential costs, try the Azure pricing calculator.

  • Webhook 触发器:此触发器等待客户端将请求发送到特定终结点。Webhook trigger: This trigger waits for a client to send a request to a specific endpoint. 发送到 webhook 终结点的每个请求都会计为操作执行。Each request sent to the webhook endpoint counts as an action execution. 例如,请求和 HTTP Webhook 触发器都是 Webhook 触发器。For example, the Request and HTTP Webhook trigger are both webhook triggers.

  • 定期触发器:此触发器根据你在触发器中设置的重复间隔创建逻辑应用实例。Recurrence trigger: This trigger creates a logic app instance based on the recurrence interval that you set up in the trigger. 例如,可以设置每隔三天或按更复杂的计划运行的定期触发器。For example, you can set up a Recurrence trigger that runs every three days or on a more complex schedule.

操作Actions

作为本机操作的 Azure 逻辑应用计量 "内置" 操作,例如 HTTP。Azure Logic Apps meters "built-in" actions, such as HTTP, as native actions. 例如,内置操作包括 HTTP 调用、来自 Azure Functions 或 API 管理的调用和控制流步骤,如条件、循环和 switch 语句。For example, built-in actions include HTTP calls, calls from Azure Functions or API Management, and control flow steps such as conditions, loops, and switch statements. 每个操作都具有其自己的操作类型。Each action has their own action type. 例如,调用连接器的操作的类型为 "ApiConnection"。For example, actions that call connectors have the "ApiConnection" type. 这些连接器分类为标准或企业连接器,根据各自的定价进行计费。These connectors are classified as Standard or Enterprise connectors, which are metered based on their respective pricing. 预览版中的企业连接器按标准连接器收费。Enterprise connectors in Preview are charged as Standard connectors.

Azure 逻辑应用将所有成功和失败的操作作为执行进行计量。Azure Logic Apps meters all successful and unsuccessful actions as executions. 但是,逻辑应用不会计量这些操作:However, Logic Apps doesn't meter these actions:

  • 由于未满足条件而跳过的操作Actions that get skipped due to unmet conditions
  • 由于逻辑应用在完成之前停止而未运行的操作Actions that don't run because the logic app stopped before finishing

对于在循环内运行的操作,Azure 逻辑应用会对循环中每个循环的每个操作进行计数。For actions that run inside loops, Azure Logic Apps counts each action for each cycle in the loop. 例如,假设有一个处理列表的“每个”循环。For example, suppose you have a "for each" loop that processes a list. 逻辑应用通过将列表项的数量乘以循环中的操作数来计量该循环中的操作,并加上启动循环的操作。Logic Apps meters an action in that loop by multiplying the number of list items with the number of actions in the loop, and adds the action that starts the loop. 因此,10项列表的计算结果为(10 * 1) + 1,这将导致执行11次操作。So, the calculation for a 10-item list is (10 * 1) + 1, which results in 11 action executions.

已禁用逻辑应用Disabled logic apps

禁用的逻辑应用不收费,因为它们在禁用时无法创建新的实例。Disabled logic apps aren't charged because they can't create new instances while they're disabled. 禁用逻辑应用后,当前正在运行的实例可能需要在一段时间之后才会完全停止。After you disable a logic app, any currently running instances might take some time before they completely stop.

集成帐户Integration accounts

固定定价模型适用于集成帐户,可在其中浏览、开发和测试 Azure 逻辑应用中的B2B 和 EDIXML 处理功能,无需额外付费。A fixed pricing model applies to integration accounts where you can explore, develop, and test the B2B and EDI and XML processing features in Azure Logic Apps at no additional cost. 每个 Azure 订阅最多可以有特定的集成帐户限制Each Azure subscription can have up to a specific limit of integration accounts. 每个集成帐户最多可存储项目的特定限制,包括贸易合作伙伴、协议、地图、架构、程序集、证书、批配置等。Each integration account can store up to specific limit of artifacts, which include trading partners, agreements, maps, schemas, assemblies, certificates, batch configurations, and so on.

Azure 逻辑应用提供免费、基本和标准集成帐户。Azure Logic Apps offers Free, Basic, and Standard integration accounts. 逻辑应用服务级别协议(SLA)支持 "基本" 和 "标准" 级别,而 "免费" 级别不受 SLA 支持,并具有吞吐量和使用限制。The Basic and Standard tiers are supported by the Logic Apps service-level agreement (SLA), while the Free tier is not supported by an SLA and has limits on throughput and usage. 除了免费层集成帐户之外,每个 Azure 区域中可以有多个集成帐户。Except for Free tier integration accounts, you can have more than one integration account in each Azure region. 有关定价费率,请参阅逻辑应用定价For pricing rates, see Logic Apps pricing.

如果有 integration service 环境(ISE)高级或开发人员),ISE 可以有5个集成帐户。If you have an integration service environment (ISE), either Premium or Developer, your ISE can have 5 total integration accounts. 若要了解如何为 ISE 使用固定定价模型,请参阅本主题前面的固定定价模型部分。To learn how the fixed pricing model works for an ISE, see the previous Fixed pricing model section in this topic. 有关定价费率,请参阅逻辑应用定价For pricing rates, see Logic Apps pricing.

若要在免费、基本或标准集成帐户之间进行选择,请查看这些用例说明:To choose between a Free, Basic, or Standard integration account, review these use case descriptions:

  • 免费:要尝试探索方案,而不是生产方案Free: For when you want to try exploratory scenarios, not production scenarios

  • 基本:仅当你只希望消息处理或充当与较大业务实体的贸易合作伙伴关系的小型企业合作伙伴时,Basic: For when you want only message handling or to act as a small business partner that has a trading partner relationship with a larger business entity

  • 标准:如果你具有更复杂的 B2B 关系并增加了你必须管理的实体数量,Standard: For when you have more complex B2B relationships and increased numbers of entities that you must manage

数据保留Data retention

除了在 integration service 环境(ISE)中运行的逻辑应用,逻辑应用的运行历史记录中存储的所有输入和输出都基于逻辑应用的运行保持期进行计费。Except for logic apps that run in an integration service environment (ISE), all the inputs and outputs that are stored in your logic app's run history get billed based on a logic app's run retention period. 在 ISE 中运行的逻辑应用不会产生数据保留成本。Logic apps that run in an ISE don't incur data retention costs. 有关定价费率,请参阅逻辑应用定价For pricing rates, see Logic Apps pricing.

为了帮助你监视逻辑应用的存储消耗,你可以:To help you monitor your logic app's storage consumption, you can:

  • 查看逻辑应用每月使用的存储单元数(以 GB 为单位)。View the number of storage units in GB that your logic app uses monthly.
  • 查看逻辑应用的运行历史记录中特定操作的输入和输出的大小。View the sizes for a specific action's inputs and outputs in your logic app's run history.

查看逻辑应用存储消耗View logic app storage consumption

  1. 在 Azure 门户中,查找并打开逻辑应用。In the Azure portal, find and open your logic app.

  2. 从逻辑应用的菜单的 "监视" 下,选择 "指标"。From your logic app's menu, under Monitoring, select Metrics.

  3. 在右侧窗格中的 "图表标题" 下,从 "指标" 列表中,选择 "计费使用情况" 执行存储消耗In the right-hand pane, under Chart Title, from the Metric list, select Billing Usage for Storage Consumption Executions.

    此指标提供按每月计费的存储消耗单位数。This metric gives you the number of storage consumption units in GB per month that are getting billed.

查看操作输入和输出大小View action input and output sizes

  1. 在 Azure 门户中,查找并打开逻辑应用。In the Azure portal, find and open your logic app.

  2. 在逻辑应用的菜单上,选择 "概述"。On your logic app's menu, select Overview.

  3. 在右侧窗格中的 "运行历史记录" 下,选择包含要检查的输入和输出的运行。In the right-hand pane, under Runs history, select the run that has the inputs and outputs you want to check.

  4. 在 "逻辑应用运行" 下,选择 "运行详细信息"。Under Logic app run, choose Run Details.

  5. 在 "逻辑应用运行详细信息" 窗格中,在 "操作" 表中列出每个操作的状态和持续时间,选择要查看的操作。In the Logic app run details pane, in the actions table, which lists each action's status and duration, select the action you want to view.

  6. 在 "逻辑应用操作" 窗格中,查找该操作的输入和输出分别出现在 "输入链接" 和 "输出" 链接下的大小。In the Logic app action pane, find the sizes for that action's inputs and outputs appear respectively under Inputs link and Outputs link.

后续步骤Next steps