Feature Request: IPv6 Support for Veeam Data Cloud for Microsoft 365 Portal Access

[alen88]

Currently, the solution only allows IPv4 ranges to be specified for portal access restrictions. As our organization and many others use IPv6 as our public IP, we are unable to limit access by IPv6 range. This is a significant security concern and does not align with modern network practices. Please add support for IPv6 address ranges in the access restriction settings.

Veeam Data Cloud for Microsoft 365 currently allows administrators to restrict portal access by specifying allowed IP ranges. However, this feature is limited to IPv4 addresses. If your organization like ours uses IPv6 as its public-facing address, you cannot restrict access based on IPv6 ranges. This limitation is a significant concern for organizations that have adopted IPv6, as it prevents them from enforcing modern network security best practices.

Over the past few days, I have been implementing Veeam Data Cloud for Microsoft 365. While I encountered several impressive features and identified some valuable enhancement opportunities, one issue stands out as particularly concerning from a security perspective. Despite the platform’s robust capabilities, it currently does not support restricting portal access by IPv6 address ranges. In today’s environment, where many organizations—including ours—leverage IPv6 for public-facing infrastructure, this limitation poses a significant security risk. The inability to define IPv6-based access controls undermines the effectiveness of network perimeter defenses and leaves a critical gap in the solution’s security posture.

I also raised a case: Case #07742914.

Thank you

[Mildur]

Hi Alen,

Great request.

I'm not sure if Veeam Data Cloud supports IPv6 fully today.
While the Portal from the original VDC environment (https://******.veeamdatacloud.com/) has IPv6 endpoints, the new VDC One UI (cloud.veeam.com) is only reachable through IPv4 addresses (tested by nslookup).

I'll share your feedback with our VDC team and make a note about your request in our internal Feature Request system.

Best,
Fabian

[alen88]

That's correct: it does not support IPv6. To make matters worse, the documentation does not mention IPv6 at all—neither confirming support nor denying it. This is a significant issue for us because, as a vendor, we use IPv6 addresses externally alongside IPv4. We are currently unable to add our IPv6 addresses to the allowed list while blocking all other traffic. Given the ongoing exhaustion of IPv4 addresses, I anticipate this will soon become a widespread problem across the industry.

[Mildur]

Hi Alen

Understood.
I already have shared the request with our internal VDC team.

Best,
Fabian