Microsoft / azure purview

Prasant Chettri 66 Reputation points
2024-11-25T05:45:41.71+00:00

I am planning to find the best landing zone strategy for Purview deployment. However, Azure purview deployment map is completely isolated from Azure landing zone map. The new landing zone has Platform - Identity, Management (shared resources), Connectivity and Application landing zone. Based on new Landing zone architecture the only plance I think of deploying Purview or SHIR in hte management (share) Landing zone vnet. Would it be the best approach for purview and SHIR and deployment.

Addtionally, when using Managed Virtual Network (Managed VNet) with Azure Integration Runtime (IR) in Microsoft Purview, the underlying virtual network is fully managed by Microsoft. This means you don't get visibility or control over its IP address range, subnets, or network configuration.

Considering, I do not have any control over to plan the flow of purview based traffic from Azure VWAN, I guess the best option to have control is to deploy SHIR on prem and cloud private network deployment

Also, are there any documentation on size recommedation for SHIR. E.g what happens to single SHIR VM that configured to scan through 10 different SQL DB, 15 different MI, 5 cosmos DB, 5 SAP hana, 3 terradata, 7 Oracle DB. What will be impact of using single VM with 10 core and 32 GB RAM. Would it be better to deploy with Scaleset and lB if it is scanning volumous Azure DB resources. Would ILB with Scaleset cause asymetric traffic issue?

Microsoft Purview
Microsoft Purview
A Microsoft data governance service that helps manage and govern on-premises, multicloud, and software-as-a-service data. Previously known as Azure Purview.
1,251 questions
0 comments No comments
{count} votes

Accepted answer
  1. Ganesh Gurram 1,510 Reputation points Microsoft Vendor
    2024-11-25T20:10:33.51+00:00

    @Prasant Chettri - Thanks for the question and using MS Q&A forum.

    While the current Azure Landing Zone architecture doesn't explicitly accommodate Purview or SHIR, placing them in the Management Landing Zone VNet is a reasonable approach. This aligns with their shared services nature and can provide centralized management and security.

    However, it's crucial to consider the specific security and network requirements of Purview and SHIR to ensure proper isolation. You may need to implement additional network segmentation and security controls to protect sensitive data and prevent unauthorized access.

    Managed Virtual Network Considerations:

    The limitations of Managed Virtual Network (MVN) can impact your ability to control the underlying network configuration. If you require fine-grained network control, you may want to explore alternative deployment options, such as:

    • Hybrid Deployment: Deploying SHIR on-premises or in a cloud-private network can provide greater control over network configuration and security.
    • Custom Network Configuration: If possible, work with Microsoft to customize the MVN configuration to meet your specific needs.

    SHIR Sizing and Scaling:

    The optimal SHIR configuration depends on several factors:

    • Data Source Volume and Complexity: The number and size of data sources, as well as their complexity, will significantly impact the required resources.
    • Scan Frequency: More frequent scans will require more processing power.
    • Workload Complexity: The types of transformations and analyses performed by SHIR will influence resource requirements.

    A single VM with 10 cores and 32 GB RAM might be sufficient for smaller-scale deployments, but for larger-scale and complex scenarios, consider scaling with a scale set and load balancer.

    ILB with Scale Set and Asymmetric Traffic:

    While ILB with a scale set can provide scalability and high availability, it's important to be aware of potential asymmetric traffic issues. To mitigate these issues:

    • Configure Proper Load Balancing: Ensure that the load balancer is configured to distribute traffic evenly across the scale set instances.
    • Monitor Traffic Distribution: Use monitoring tools to track traffic distribution and identify any imbalances.
    • Consider Session Affinity: If required, implement session affinity to maintain session state across multiple instances.

    By carefully considering these factors and following best practices, you can effectively deploy and manage Microsoft Purview to gain valuable insights from your data assets.

    Hope this helps. Do let us know if you have any further queries.


    If this answers your query, do click `Accept Answer` and `Yes` for was this answer helpful. And, if you have any further query do let us know.

    0 comments No comments

0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.