Jonathan Bailey's questions

I've set up an Azure virtual machine in a virtual network, and have joined it to an Azure AD Domain Services domain. The virtual network uses the AADDS DNS servers.

I've created a private link to connect to an Azure storage account file service in the virtual network, and I can confirm that it has an IP address in the subnet to which the virtual machine is connected.

However, from the virtual machine, the FQDN of the file share, storageaccountname.file.core.windows.net still resolves to the public IP address. This makes sense to me because there's no DNS record in the AADDS server for the private link. How do I configure the DNS so that the VM connects to the file service through the private link?

Edit: DNS won't even resolve to the private endpoint IP address if I add a record to the hosts file.

We've recently migrated a system off of a set of EC2 instances, and now wish to retire those EC2 instances, first by creating an AMI of and then terminating each EC2 instance.

Over time, we've created a number of EBS snapshots of the volumes attached to the EC2 instances as a part of our maintenance strategy.

Will the EBS snapshots referenced by the AMIs we create be independent of the maintenance EBS snapshots? In other words, will the EBS snapshots referenced by the AMIs have pointers back to the most recent maintenance EBS snapshots, or will they reference the relevant blocks independently of the maintenance EBS snapshots?

Ultimately, I'm trying to determine whether, once the AMIs are created, if it is useful or worthwhile to delete the maintenance EBS snapshots from a cost and management overhead perspective.

I've created an Azure VM and joined it to the Azure AD domain. I've enabled Azure AD login on the VM, and added users to the Azure AD AAD DC Administrators group, which is assigned the Administrator role in the VM.

I can RDP to the VM as a user in the AAD DC Administrators group that is a member of the Azure AD domain. However, I cannot RDP to the VM as a user in the group that is a guest user in the Azure AD domain. When I attempt to do so, the RDP client indicates that the credentials are incorrect for the guest user:

The credentials that were used to connect to did not work. Please enter new credentials.

I've verified that the credentials that I'm supplying are correct. I'm trying to determine if it's because:

1. the format of the credentials that I'm supplying is incorrect (e.g,. should I use Domain\user.name, or [email protected], or Domain\[email protected]);
2. it's a password hah sync problem (this is a cloud-only account); or,
3. it's not possible to do this.