Enabling Mobile Apps for Multi-Server Licensing

Most companies set up the AADAP to connect to one server, so usually only one person, typically the database administrator, enables mobile apps. However, if you allocate licenses across multiple servers—for example, you have several corporate offices and provide separate licenses for each office—you need to enable mobile apps in a particular order, as described in this article.

Note: These instructions also apply to business partners who share license uses with a number of consultants.

The principal license holder enables mobile apps first

Before other users enable mobile apps, the principal license holder—the licensee of record—needs to set up a communication channel to the Sage 100 Contractor “back office,” as follows:

  1. In Database Administration, click Server Management > Enable Sage Mobile Apps.

  2. On the Enable Sage Mobile Apps tab, click [Request Azure AD] to request an Azure account.

    The request is sent to our Cloud Enablement team, which sends you an email inviting you to set up your Azure account. The email will come from SageSolutionsAdministrator.

    Note: This email is sent to the principal license holder. If another user (for example, a consultant) tries to request an AAD account first, the principal license holder might receive the invitation email from Sage not knowing why they’re receiving it or what to do next, while the user waits in vain to receive the invitation.

  3. After setting up the AAD account, click [Install Proxy] to install the AAD Application Proxy (AADAP) on your computer.

    The AADAP enables communication with mobile phones.

  4. Share the AAD credentials with the other users (such as branch offices or consultants), who need these credentials to set up AADAPs on their own computers.

Other users enable mobile apps on their servers, later

Other users, such as consultants and managers of branch offices, can now use the AAD credentials to set up new AADAPs, as follows:

  1. In Database Administration, click [Request Azure AD].

    Note: Don’t wait for an invitation email from Sage because you will not receive one. The principal license holder has already set up the account.

  2. Click [Install Proxy].