Hybrid Connection Widget
The Hybrid connection widget on the Dashboard screen shows issues with the hybrid connection. The widget state is synchronized automatically every time the page is refreshed.
When a customer does not want to configure a hybrid connection with Quest Recovery Manager for Active Directory, the corresponding connection error events can be deactivated by changing their severity from Error to Info. To do this, clear the Show hybrid restore errors if hybrid connection is not configured check box in the Configure hybrid connection dialog. For details, see Integration with Recovery Manager for Active Directory.
The widget has the following states:
- If the hybrid connection is properly configured and works fine, the widget is green.
- If the hybrid connection is not configured because you do not need it, the widget is gray and advises you to configure the connection. In this case, the Show hybrid restore errors if hybrid connection is not configured check box is not selected in the Configure hybrid connection dialog.
- If the hybrid connection is not configured and the Show hybrid restore errors if hybrid connection is not configured check box is selected in the Configure hybrid connection dialog, the widget is yellow and has a warning sign.
- If one or more console is connected to On Demand Recovery and the Show hybrid restore errors if hybrid connection check box is selected in the Configure hybrid connection dialog, the widget is yellow and has a warning sign. For more information, go to the Configure Hybrid Recovery section in Hybrid Recovery with On Demand Recovery.
Working with Inactive Mailboxes
Working with Inactive Mailboxes
On Demand Recovery supports restore of inactive mailboxes of hard-deleted users. The Federated Domain scenario is also supported. This feature requires Recovery Manager for Active Directory 9.0 or higher.
To preserve the original cloud mailbox of a hybrid user after restore, you have to select the If a hybrid user already exists in Azure Active Directory, delete it before the restore operation option in the Restore Object dialog.
User scenario
- There is a hybrid user. This user is deactivated by the administrator for some reason. This means that the user account goes to the Recycle Bin. After 30 days, Azure AD cleans this account from the Recycle Bin.
- Then, the user returns and the account is enabled again by the administrator. After the activation, the user is recreated in the cloud with the new mailbox.
- We want to use the original cloud mailbox for the user. The only one way to do this is to restore the user from the backup. But before the restore, the newly created cloud user must be removed from Azure AD using this new option.
If you restore a hybrid user and their mailbox with On Demand Recovery
- For Non-Federated Domains, On Demand Recovery restores a cloud user and its mailbox without an on-premises user.
- For Federated Domains, restore of hybrid users requires Recovery Manager for Active Directory. In this scenario, On Demand Recovery restores a hybrid user and its mailbox in the cloud. Recovery Manager for Active Directory restores this hybrid user on premises, then it calls Azure AD Connect to synchronize the user back to the cloud and make the cloud user previously restored by On Demand Recovery be in the Federated Domain. Without Recovery Manager for Active Directory, the cloud user will be non-federated after restore and you will not log in with this user.
Hybrid Connection Port and Protocol Requirements
Hybrid Connection Port and Protocol Requirements
Hybrid configuration with Recovery Manager for Active Directory requires only outbound TCP/UDP port 443 to be opened on the Recovery Manager Portal server to access the internet. If the Recovery Manager Portal server already has access to the internet, you do not need to change the Firewall configuration.
|
|
Note: If you do not want to open all outbound IP Prefixes and your firewall or proxy allows DNS allow lists, you can add connections to <your name space>.servicebus.windows.net to your allow list. |
Table 3: Hybrid connection port and protocol requirements
| HTTPS |
443 (TCP/UDP) |
Outbound |
Figure 2: Hybrid Restore Components Diagram
Hybrid Connection Security
FIPS 140-2 compliant TLS protocol is used for traffic encryption. HTTPS certificate is validated on our client side (Recovery Manager Portal).
Server side is Azure WCF Relay that is created and configured in Quest Azure Subscription.
Shared Access Signature (SAS) is used for authentication. A SAS token is based on an access key generated by On Demand Recovery cloud. This key is downloaded to the on-premises server with Recovery Manager Portal and used in the portal configuration to establish the Hybrid connection (from on-premises to the cloud). The SAS token is sent to the cloud and verified on each connection request. For details about Shared Access Signature algorithm, click the following link: https://docs.microsoft.com/en-us/azure/service-bus-relay/relay-authentication-and-authorization.
