Complete AZ-720 Microsoft Materials

• Connection: VNet1-VNet4 Parameters are: AllowGatewayTransit: Enabled

• Connection: VNet4-VNet1 Parameters are: UseRemoteGateways: Enabled

To resolve the connectivity issues for VM1 to Contoso Suites, you need to configure the peering connections between VNet1 and VNet4 correctly. The peering connection from VNet1 to VNet4 should have the AllowGatewayTransit parameter enabled, which allows VNet1 to use the virtual network gateway in VNet4 as a transit point for traffic. The peering connection from VNet4 to VNet1 should have the UseRemoteGateways parameter enabled, which allows VNet4 to use the remote gateway in VNet1 for traffic destined to Contoso Suites. The IP Allocation parameter should be set to Dynamic for both peering connections, which allows Azure to assign IP addresses from the address space of the peered virtual network. The ServiceEndpoint parameter should be set to None for both peering connections, as there is no need to enable service endpoints for this scenario.

The error 8344 insufficient access rights to perform the operation indicates that the Azure AD Connect service account does not have the required permissions to synchronize the Admin1 account. This could be because the Admin1 account is in an organizational unit (OU) that has security inheritance disabled, which prevents the service account from inheriting the necessary permissions from the parent OU. To resolve this issue, you should enable security inheritance in AD DS for the OU that contains the Admin1 account. This will allow the service account to synchronize the Admin1 account to Azure AD. Alternatively, you could also grant the service account explicit permissions on the Admin1 account, but this would be more tedious and less scalable than enabling security inheritance.

To resolve the problem reported by User2, you need to assign an Azure AD Premium P1 license to User2. User2 is a member of the warehouse group, which is enabled for the self-service password reset (SSPR) feature. However, User2 cannot register for SSPR because they do not have a valid license that supports SSPR. To use SSPR, a user must have one of the following licenses: Azure AD Premium P1, Azure AD Premium P2, Enterprise Mobility + Security (EMS) E3 or EMS E5. By assigning an Azure AD Premium P1 license to User2, you can enable them to use the SSPR feature and reset their password without contacting the helpdesk

To troubleshoot the issue with SRV2, you need to run the Get-MsolServicePrincipalCredential PowerShell cmdlet, which returns the credentials that are associated with a service principal in Azure AD. The service principal is an identity that represents an application or a service that interacts with Azure AD. In this case, the service principal is used by the NPS extension for Azure AD MFA to communicate with Azure AD and perform MFA requests. The credentials of the service principal include a certificate and a key that are used to authenticate the service principal to Azure AD. If the credentials are expired or invalid, the MFA requests will fail with a security token error. To resolve this issue, you need to renew the credentials of the service principal by using the New-MsolServicePrincipalCredential cmdlet.