u/Dear_Signature_9602

Hi Team,

What is the general consensus on design decisions related to controls and restrictions against communication between subnets within vNets?Using NSGs or routing tables/rules vs multiple vNets with one per subnet? Looking at cost considerations when peering multiple vNets and simplicity to manage and other but at the same time having that zero-trust mindset. This is for both hub/spoke and vWAN architectures.

DFS Namespace with root-consolidation works a treat for on-premises file server migrations moving to Azure Files or similar. DFS Namespace in a failover cluster environment adds the extra level of redundancy and availability. What if we have cloud-native environments or want to move this off traditional on-premises environments to Azure? do we just build the same environment on IaaS or can we trim down and build better?

Hi Team,

Looking for assistance to restore configuration backup to newly deployed VBR 13 software hardened appliance. Configuration backups are stored on a separate Veeam Hardened Repository in a DR location and not in default VBR repository.

How do we download (.bco) from the VHR or make available for the new VBR?

Hey team,

Looking for help to answer and recommend the below please.

Scenario: Azure Files with storage account configured with Kerberos identity authentication. File shares are a result of robocopy migration from windows file server shares with NTFS. Using private endpoints. Devices accessing are Entra-joined. Some groups that users are members of show up as an orphaned SID as it has been replaced by new SID (maybe internal migration) and SID for group on-prem is newer. Entra connect sync from on-prem not linking the two in Entra.

1. Does Azure Files with Entra Kerberos support ACL translation using group SIDHistory? or is this honoured by attributes available in user token? can it be enabled and are there any risks to be aware of?
2. What is the best way to handle orphaned groups in Entra that have been granted NTFS permissions on Azure files but not groups that sync to Entra? i.e. Builtin\Administrators, CONTOSO\domain users or CONTOSO\Domain Admins.

Hey team,

Looking for help to answer and recommend the below please.

Scenario: Azure Files with storage account configured with Kerberos identity authentication. File shares are a result of robocopy migration from windows file server shares with NTFS. Using private endpoints. Devices accessing are Entra-joined. Some groups that users are members of show up as an orphaned SID as it has been replaced by new SID (maybe internal migration) and SID for group on-prem is newer. Entra connect sync from on-prem not linking the two in Entra.

1. Does Azure Files with Entra Kerberos support ACL translation using group SIDHistory? or is this honoured by attributes available in user token? can it be enabled and are there any risks to be aware of?

2. What is the best way to handle orphaned groups in Entra that have been granted NTFS permissions on Azure files but not groups that sync to Entra? i.e. Builtin\Administrators, CONTOSO\domain users or CONTOSO\Domain Admins.

Hi All, checking if it is true that Veeam cloud vault managed archive tier is becoming available? at the moment I believe it is a manual process to create the Azure storage tier in own tenant and add to SOBR. The Veeam Cloud vault currently has a managed capacity-tier but would like to offload to Azure archive-tier if possible and not have to self-manage the infrastructure. This may not be available and on the road map but hoping soon.

Hey everyone - trying to add a Hyper-V cluster using cluster name to newly installed Veeam Backup & Replication built using 'Veeam Software Appliance 13.0.2.29' with default settings and not joined to AD domain. Tried to use the UPN style format and modify the Krb5.conf as per the below KB. DNS is resolving OK.

https://preview.redd.it/91j5665phabh1.png?width=480&format=png&auto=webp&s=32e7f393d98688e7edffc0ddfa1d040982e30002

KB4841: How to Configure krb5.conf for Cross-Domain Hyper-V Cluster Management