Skip to content

Commit dede5e5

Browse files
Merge pull request #214657 from lrtoyou1223/vnetirbranch34
Add note in managed vnet
2 parents 44da46f + 8c2dc61 commit dede5e5

File tree

2 files changed

+3
-0
lines changed

2 files changed

+3
-0
lines changed

articles/data-factory/managed-virtual-network-private-endpoint.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -121,6 +121,8 @@ The following table lists the differences between different types of TTL:
121121
| Can be disabled | Y | Y | N |
122122
| Reserved compute is configurable | N | Y | N |
123123

124+
> [!NOTE]
125+
> You can't enable TTL in default auto-resolve Azure integration runtime. You can create a new Azure integration runtime for it.
124126
125127
## Create a managed virtual network via Azure PowerShell
126128

includes/azure-data-factory-limits.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -23,6 +23,7 @@ Azure Data Factory is a multitenant service that has the following default limit
2323
| Concurrent Pipeline activity runs per subscription per [Azure Integration Runtime region](../articles/data-factory/concepts-integration-runtime.md#azure-ir-location) <br><small>Pipeline activities execute on integration runtime, including Lookup, GetMetadata, and Delete. This limit does not apply to Self-hosted IR.</small> | 1,000 | 1,000 |
2424
| Concurrent authoring operations per subscription per [Azure Integration Runtime region](../articles/data-factory/concepts-integration-runtime.md#azure-ir-location)<br><small>Including test connection, browse folder list and table list, preview data. This limit does not apply to Self-hosted IR.</small> | 200 | 200 |
2525
| Concurrent Data Integration Units<sup>1</sup> consumption per subscription per [Azure Integration Runtime region](../articles/data-factory/concepts-integration-runtime.md#integration-runtime-location)| Region group 1<sup>2</sup>: 6,000<br>Region group 2<sup>2</sup>: 3,000<br>Region group 3<sup>2</sup>: 1,500<br>Managed virtual network<sup>2</sup>: 2,400 | Region group 1<sup>2</sup>: 6,000<br/>Region group 2<sup>2</sup>: 3,000<br/>Region group 3<sup>2</sup>: 1,500<br>Managed virtual network: [Contact support](https://azure.microsoft.com/blog/2014/06/04/azure-limits-quotas-increase-requests/). |
26+
| Concurrent Data Integration Units<sup>1</sup> consumption per subscription per [Azure Integration Runtime region](../articles/data-factory/concepts-integration-runtime.md#integration-runtime-location) in managed virtual network| 2,400 | [Contact support](https://azure.microsoft.com/blog/2014/06/04/azure-limits-quotas-increase-requests/). |
2627
| Maximum activities per pipeline, which includes inner activities for containers | 40 | 40 |
2728
| Maximum number of linked integration runtimes that can be created against a single self-hosted integration runtime | 100 | [Contact support](https://azure.microsoft.com/blog/2014/06/04/azure-limits-quotas-increase-requests/). |
2829
| Maximum number of node that can be created against a single self-hosted integration runtime | 4 | [Contact support](https://azure.microsoft.com/blog/2014/06/04/azure-limits-quotas-increase-requests/) |

0 commit comments

Comments
 (0)