# Connecting the OpenZeppelin CLI to an Azure PoA Network

**URL:** <https://forum.openzeppelin.com/t/connecting-the-openzeppelin-cli-to-an-azure-poa-network/2346>\
**Category:** SDK\
**Created:** [February 23, 2020, 6:57pm UTC](https://forum.openzeppelin.com/t/connecting-the-openzeppelin-cli-to-an-azure-poa-network/2346 "2020-02-23T18:57:49Z")\
**Posts on this page:** 1\
**Showing post:** 16

<div class="post-metadata">

**Author:** ![MWaser](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.openzeppelin.com/mwaser/32/1677_2.png) [@MWaser](https://forum.openzeppelin.com/u/MWaser)\
**Post date:** [February 25, 2020, 1:24pm UTC](https://forum.openzeppelin.com/t/connecting-the-openzeppelin-cli-to-an-azure-poa-network/2346/16 "2020-02-25T13:24:01Z")

</div>

So . . . my next challenge is that

Additionally, there is a separate, unconfigurable [data size limit](https://ethereum.stackexchange.com/questions/59054/increase-maxcodesize-in-ethereum-private-network)for deploying new contracts. If your transaction involves deploying a new contract, it will be restricted to 48 KB.

Thanks

Microsoft Azure Blockchain Team  
Wednesday, January 2, 2019 9:25 PM

Is there an easy way to break up and deploy the prerequisite upgradeable contract packages?

[Project description in next reply]

---

_[View the full topic](https://forum.openzeppelin.com/t/connecting-the-openzeppelin-cli-to-an-azure-poa-network/2346)._