Follow instructions to manually register the App: You must perform the steps in Manually registering the MNE application with the Microsoft Entra admin center to register Migrator for Notes to Exchange with the Microsoft Entra admin center site. After App registration is complete, you will need to provide the following information from the Microsoft Entra admin center.
• |
Tenant Domain Name: Your tenant’s primary domain name on the Microsoft Entra admin center. For example, Sitraka.onmicrosoft.com. |
• |
Tenant ID: Your tenant’s ID, found on the Home page of the Microsoft Entra admin center. |
• |
Registered App Client ID (SSDM): The application ID created with delegated permissions after the application is registered in the Microsoft Entra admin center. With the manual registration process, the client ID that you enter for the SSDM is the same as the Registered App Client ID. |
• |
Registered App Client ID: The Application ID created with application permissions after the application is registered in the Microsoft Entra admin center. |
• |
Registered App Client Secret: The Application Secret created after the application is registered in the Microsoft Entra admin center. |
Show App Client Secret: When the check box is selected, the App Client Secret value is not masked but is displayed so that you can make note of the client secret value to use if you are manually registering the application with Microsoft Entra.
The process of registering an application with the Microsoft Entra admin center is also described in the Microsoft Learn topic Register an application in Microsoft Entra ID.
3 |
On the Register an application page, enter the application registration information: |
• |
Name: For example, Quest Migrator for Notes to Exchange. |
• |
Supported account types: Select Accounts in any organizational directory (Any Microsoft Entra ID tenant - Multitenant) |
• |
Select Public client/native (mobile & desktop) |
• |
Enter a URI: https://login.microsoftonline.com/common/oauth2/nativeclient |
4 |
Choose Register. |
• |
Application (client) ID: The Application ID created after the application is registered in the Microsoft Entra admin center. You must copy this ID and use it later to complete the App Registration. |
5 |
Under Manage in the left side menu, choose API permissions. Under Configured permissions choose Add a permission. |
a |
Select Application permissions on the right. We will grant Delegated permissions in a following step. |
• |
From Select permissions, filter on Directory., then expand Directory and select Directory.ReadWrite.All. Choose Add permissions to grant application permission. |
• |
From Select permissions, filter on Mail., the expand Mail and select Mail.Send. Choose Add permissions to grant application permission. |
• |
• |
• |
From Select permissions, filter on Files., then expand Files and select Files.ReadWrite.All. Choose Add permissions to grant application permission. |
c |
Go back to add a permission for Microsoft Graph under Microsoft APIs and select the left box Delegated permissions. |
• |
From the list, expand Openid permissions, and select each of: |
• |
openid, and |
• |
• |
From Select permissions, filter on Directory., then expand Directory and select Directory.AccessAsUser.All. Choose Add permissions to grant application permission. |
• |
From Select permissions, filter on Files., then expand Files and select Files.ReadWrite. Choose Add permissions to grant application permission. |
7 |
Under Configured permissions choose Add a permission. On the Request API permissions window on the right, under APIs my organization uses, enter the API name Office 365 Exchange Online. Select this row. |
a |
Select Application permissions on the right. |
• |
Exchange.ManageAsApp, under Exchange and |
• |
full_access_as_app under Other permissions. |
API / Permission name |
|||
9 |
Under Manage in the left side menu, choose Certificates & secrets. |
a |
Under Client secrets, choose New client secret |
c |
Choose Add to generate the client secret. |
10 |
Under Manage in the left side menu, select API permissions. |
11 |
12 |
In the Microsoft Entra admin center’s left side pane, select Roles & admins. On the Roles and administrators | All roles page, |
13 |
Your MNE app registration is complete. On the left side menu, choose Overview to obtain settings for the next step. |
14 |
On the Microsoft Azure App Registration page in MNE, enter the values that were assigned for: |
• |
Tenant Domain Name: Your Microsoft 365 tenant domain name. For example, Sitraka.onmicrosoft.com. |
• |
Tenant ID: Your tenant’s ID, found on the Home page of the Microsoft Entra admin center. |
• |
Registered App Client ID (SSDM): The application ID created with delegated permissions after the application is registered in the Microsoft Entra admin center. With the manual registration process, the client ID that you enter for the SSDM is the same as the Registered App Client ID. |
• |
Registered App Client ID: The Application ID created with application permissions after the application is registered in the Microsoft Entra admin center. |
• |
Registered App Client Secret: The Application Secret created after the application is registered in the Microsoft Entra admin center. |
15 |
Click Save. |
Click Apply after you enter new information or changes to existing information. The program does not read or save any new information or changes until Apply is clicked.
• |
Automatically grant permissions: The access credentials must be an Active Directory administrative account that is a member of the Exchange Organization Management role group, is configured with remote PowerShell enabled, and has full access to the target Organizational Units (OUs). Quest recommends that customers not enable this check box unless directed by Quest support personnel. |
• |
Global Catalog host name: Specify a Global Catalog (GC) at a level higher than all the users, groups, and contacts to be migrated. If you have multiple Global Catalogs/Domain Controllers in an AD forest, you can choose any GC as long as it is in the same domain. |
• |
Domain Controller host name Specify the Domain Controller that is used to read data from or write data to Active Directory. |
• |
User name and Password: The access credentials used to authenticate the administrator by whose authority the program accesses Active Directory. |
• |
Always use these values: Select this check box if the wizards will always use these credentials. If this box is selected, the wizard skips the screen that requests credential information. If the check box is empty, the wizard retrieves the values entered here as defaults, but will display the screen to offer the option of accepting or changing the default credentials. |
• |
Path to existing organizational unit for distribution groups: Fully qualified domain name (FQDN) for the group organizational unit (OU) path. |
• |
Path to existing organizational unit for creating external members for distribution groups: Fully qualified domain name (FQDN) for the path for an existing organizational unit (OU) to which group members will be assigned when a member must be created as a new AD contact (when there is no corresponding AD user account). |
• |
Create user objects in Active Directory: Determines whether the Provisioning Wizard will create a new user object in AD when none is found to correspond with a user in the collection. Such new user objects are created in the container specified by the Path to existing organizational unit for creating user objects text box. Ordinarily the objects created are not mail-enabled, although the EnableUsers parameter (in Task Parameters) can be set to 1 to change that default behavior. |
• |
Path to existing organizational unit for creating user objects: Click Browse to find and specify the relative domain name for an existing organizational unit (for example, cn=users) where any new user objects will be created in AD (when a wizard encounters a contact for which there is no existing corresponding AD user account). |
• |
Use resource/user forest: If your target environment is configured for a resource forest and a user forest with corresponding user accounts, you must provide these credentials for the Data Migration Wizard to enable mailboxes and to associate the resource accounts with the user accounts. The credentials specified here identify the user forest, while the credentials specified for AD credentials pertain to the resource forest. |
NOTE: In addition to specifying the User forest credentials here, you must also add a set of parameters to the configuration data for the Data Migration Wizard, explained in Appendix A of the Migrator for Notes to Exchange Administration Guide—see the topic How do I prepare the SQL database for mailbox-enabling (if AD is configured for a resource forest and a user forest)? |
• |
Global Catalog host name: The name of the AD server. |
• |
User name: The user ID of the administrator who will be running the migration program, by whose authority the program accesses the user forest AD. This entry must be the SAM Account name, not the UPN. |
• |
Password: The password associated with the user name. |
• |
Apply: Reads and saves new or changed information. Any new information or changes are discarded if you do not click Apply before you exit. |
• |
More info: Launches the Log Viewer to display the associated log file. This button is enabled only if the program encountered significant errors or warnings that require resolution before continuing in the migration. If no significant errors or warnings are encountered, the button is dimmed (unavailable). |
© 2025 Quest Software Inc. ALL RIGHTS RESERVED. Termini di utilizzo Privacy Cookie Preference Center