Dooap for AX2012
      Back to home
      1. Knowledgebase
      2. Technical Guide
      3. Dooap for AX2012

      Technical Tasks for Dooap AX2012 Deployment

      How to deploy Dooap in AX2012? This article outlines the technical steps required to complete Dooap UAT and Dooap Production enrollment process.

      # Task Details Customer IT / Dynamics partner

      Dooap Team
      1 Provide Azure AD Dooap supports only Microsoft Entra ID (AAD) logins, read more here.      X  
      2

      Install Azure HCM

      Install Azure Hybrid Connection Manager to AX2012 AOS TEST 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  
      3 Deliver AX Model Dooap team delivers the Dooap AX Model to Customer.        X
      3.1 Install Dooap Model Install the AX Model to AX2012 TEST environment (see separate instructions here).       X  
      4 Create users

      Create users to AX2012 TEST for Dooap integration and Dooap consultants.

      NOTE: Users must be be created to LocalAXdomain.

      Dooap security policy requires separated integration accounts for testing (UAT) and production.

       

      1. Account: “Dooap UAT integration account”

      • For example: “LocalAXdomain\dooap-integration-test”
      • Roles in AX: Dooap Integration
      • Access must be to all legal entities
      • Language must be set to En-US
      • Password cannot expire as it would stop Dooap --> AX2012 integration

      2. Account: “Dooap Production integration account”

      • For example: “LocalAXdomain\dooap-integration-prod”
      • Same as above + Full AX2012 license needed

      3. Account(s): Personal accounts for Dooap consultants

      • 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 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)

       

      		    
      (4.2)

      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 Set up remote access Set up remote access to AX2012 TEST for Dooap consultants.      X  
      5.1 Set up remote access Set up remote desktop access to AX2012 TEST AOS Server for the Dooap Integration User (VPN required?). Once this is available, the Dooap team can validate the Hybrid Connection Manager setup.      X      X
      8 Install Chrome Install Chrome browser on the same server with AX2012 Client (will be used to open Dooap invoices from AX).    
      9 Consent

      Dooap team provides the consent wizard link to Customer.

      		       X
      9.1 Consent 

      Grant consent using a link provided by Dooap.

      This must be done by native global Admin.

      		      X     
      10 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 (9.1) and activating the inbound port is completed.

      		 X  
      10 Enrol

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

      		       X
        Production Repeat all the steps for enrolling the production environment, which must be completed separately before the go-live.      X      X