{"id":110936,"date":"2018-02-09T05:53:39","date_gmt":"2018-02-09T13:53:39","guid":{"rendered":"https:\/\/www.microsoft.com\/en-us\/power-platform\/blog\/power-automate\/gateway-ha-increased-apply-to-each\/"},"modified":"2018-02-09T05:53:39","modified_gmt":"2018-02-09T13:53:39","slug":"gateway-ha-increased-apply-to-each","status":"publish","type":"power-automate","link":"https:\/\/www.microsoft.com\/en-us\/power-platform\/blog\/power-automate\/gateway-ha-increased-apply-to-each\/","title":{"rendered":"Gateway High Availability and increased limits for Apply to each"},"content":{"rendered":"
Today, you can create high available clusters of on-premises data gateways, to ensure your organization can access on-premises data resources used in PowerApps and Flow. Such clusters allow gateway administrators to group gateways to avoid single points of failure in accessing on-premises data resources. Read this article<\/a> for the steps you can take to create a high availability cluster of on-premises data gateways and shares best practices when setting them up. High availability gateway clusters require the November 2017 update to on-premises data gateway, or later.<\/p>\n <\/p>\n From PowerApps or Flow, you will only see the individual gateways. If the gateways belong to a cluster, you will only see the primary gateway (also known as anchor gateway) but won\u2019t see other gateways in the same cluster. You will not see the cluster the gateways belong to from PowerApps or Flow at this time. Read more here<\/a>.<\/p>\nIncreased limits for Apply to each<\/h2>\n