[AVM Module Issue]: Update Purview to use latest API to make use of new Purview features

[DataOpsDon]

Check for previous/existing GitHub issues

• I have checked for previous/existing GitHub issues

Issue Type?

Feature Request

Module Name

avm/res/purview/account

(Optional) Module Version

No response

Description

Can we update the Purview model to utilise the latest API version? I understand that the newest API is still in preview, but the 2021 version is outdated and lacks key features needed for the AVM module. The new Purview capabilities are essential for our use case.

(Optional) Correlation Id

No response

[microsoft-github-policy-service]

Important

The "Needs: Triage 🔍" label must be removed once the triage process is complete!

Tip

For additional guidance on how to triage this issue/PR, see the BRM Issue Triage documentation.

[avm-team-linter]

@DataOpsDon, thanks for submitting this issue for the avm/res/purview/account module!

Important

A member of the @Azure/avm-res-purview-account-module-owners-bicep or @Azure/avm-res-purview-account-module-contributors-bicep team will review it soon!

[hundredacres]

@DataOpsDon getting an error when I update the resource to use a preview API

Status Message: The managed event hub namespace cannot be enabled for account ***pvamin001 from 2023-05-01-preview api version. (Code: 2010)

Let me dig around and see if there's a bug with the RP

[DataOpsDon]

Ah this is likely because in the "new world" within Purview the managed resource now live in a separate Microsoft own subscription (separate tenant), not the subscription where you have deployed Purview (in your tenant). So I suspect this is the issue.

Happy to help if needed.