v1.1.0
Templates:
- Bugfix in Bastion Host template (#167)
- Updated Purview regions (#162)
- Added Azure Machine Learning Policy to Disable Public Network Access (#175)
- Changed one Firewall network rule from FQDNs to IPs in order to overcome an error that was caused when customers deploy into an existing ESLZ environment and did not enable the DNS forwarder feature of the Firewall (#178)
- Added What-If step to validation stage of GitHub Action and Azure DevOps workflow (#185)
- Incorporated Purview DNS changes after GA of the service (#183)
Portal:
- Added Resource Provider Registration for managed Purview resources (EventHub and Storage) and Purview itself in Portal experience. This will solve some of the deployment issues that users have seen in the past when deploying the Data Management Zone or when using the all-in-one deployment option for ESA (#158 & #161).
- Updated Resource Provider Guidance in Portal (#172)
- Added option to select custom DNS forwarder even when selecting Azure Firewall as Firewall resource (#178)
Docs:
- Added cost estimates for Enterprise-Scale Analytics (#165 & #176)
- Updated guidance in Bastion Host article (#163)
- Updated guidance and images for Bastion Host connectivity (#169)
- Added Purview RP issue to "Known Issue" and provided guidance on how to overcome this (#160 and #170 and #174).
- Minor spelling error (#168)
- Added doc about how to limit cross-tenant private endpoints (#152)
- Updated network considerations doc (#176)
- Added Docs about adding Purview Root Collection Admins (#193)
Other:
- Fixed Linting for PRs opened from a forked repository (#171)