Technical Tasks for Dooap PROD AX2012 Deployment

How to deploy Dooap PROD in AX2012?


This article outlines the responsibilities and technical steps required to complete Dooap PROD enrollment process. 

 

# Task Details Customer IT / Dynamics partner

Dooap Team

0 Prerequisite for Dooap end-user authentication Dooap requires Microsoft Entra ID (AAD) for end-user login, read more here. X  
1 Provide PROD server details

Provide the following server details to the Dooap team:

  • Name of the local domain
  • Name of the AX2012 PROD AOS server (And port number, if multiple AOS instances on the same server)
  • Kernel version and Application version
X  
1.1

Create user to AX2012 PROD for Dooap integration

Account: “Dooap PROD integration account”

  • For example: “LocalAXdomain\dooap-prod”
  • Maximum length of the username is 20 characters
  •  Access must be to all legal entities
  • Language must be set to En-US
  • Password cannot expire
    • That would stop Dooap --> AX2012 integration.
X  
2

Install Azure HCM

Install Azure Hybrid Connection Manager to AX2012 AOS PROD server (Download: Azure Hybrid Connection Manager).

X  
2.1 After HCM Installation Important! After HCM Installation: Open Task Manager and set priority to ‘Realtime’. X  
2.2 Connection string for HCM

Open Hybrid Connection Manager UI and click Enter Manually and paste the connection string provided by Dooap team.

image (15)

image (16)

X  
3 Promote Dooap Model to PROD Promote the AX Model to AX2012 PROD environment.   X
4 Create users

Create users to AX2012 PROD for Dooap Consultant(s). Provide them instructions on how to access.

  • Needs to be created to LocalAXdomain.
  • Roles in AX2012: Dooap, System administrator may be needed temporarily (for setting / ensuring financial and AP parameters)
  • Password expiration according to organizations security policies
X  
4.1 Configure the PROD Integration Account
  • Assign a role in AX: Dooap Integration
  • Dooap Team will provide you an Entra account to be linked to the integration account in step 4.2.

image (17)

X  
4.2 Link users to Entra accounts

Since AX2012 is not in the cloud, a separate manual linking between AX users and their Entra accounts is needed.

All users (the integration user, end users & Dooap consultants) are required to be linked to their Entra accounts via the Dooap users function.

  • An alternative approach regarding the integration user and Dooap consultants is to create new Entra users (step 4.2).

image (8)

 

X  
(4.3)

Create users to AAD

(optional)

If steps 4 and 4.1 are followed correctly, there is no need to create new Entra users.

However, if preferred, instead of linking the Dooap consultants and Dooap integration user in step 4.1, you can create new users in Entra ID for the Dooap consultants and Dooap integration user.

Once the accounts are created, please securely send the user account credentials to the Dooap team.

X  
5 Consent

Dooap team provides the consent wizard link to Customer.

  X
5.1 Consent 

Grant consent using a link provided by Dooap.

This must be done by native global Admin.

X     
6 Inbound port activation

Activate the inbound port for DooapServices.

image (9)

Please note that activating this port will result in a brief service interruption for AX2012, lasting a few minutes. Hence, we recommend carefully planning the timing of this activation.

Ensure this step is completed in both the test and production environments.

Confirm to Dooap once granting consent and activating the inbound port is completed.

X  
7 Enrollment of Dooap tenant

Dooap team will enrol the Dooap tenant and finalize the setup.

      X