Tutorial: Configure LogMeIn for automatic user provisioning

This tutorial describes the steps you need to perform in both LogMeIn and Microsoft Entra ID to configure automatic user provisioning. When configured, Microsoft Entra ID automatically provisions and de-provisions users and groups to LogMeIn using the Microsoft Entra provisioning service. For important details on what this service does, how it works, and frequently asked questions, see Automate user provisioning and deprovisioning to SaaS applications with Microsoft Entra ID.

Capabilities Supported

• Create users in LogMeIn
• Remove users in LogMeIn when they do not require access anymore
• Keep user attributes synchronized between Microsoft Entra ID and LogMeIn
• Provision groups and group memberships in LogMeIn
• Single sign-on to LogMeIn (recommended)

Prerequisites

The scenario outlined in this tutorial assumes that you already have the following prerequisites:

• A Microsoft Entra tenant
• One of the following roles: Application Administrator, Cloud Application Administrator, or Application Owner.
• An organization created in the LogMeIn Organization Center with at least one verified domain
• A user account in the LogMeIn Organization Center with permission to configure provisioning (for example, organization administrator role with Read & Write permissions) as shown in Step 2.

Step 1: Plan your provisioning deployment

1. Learn about how the provisioning service works.
2. Determine who will be in scope for provisioning.
3. Determine what data to map between Microsoft Entra ID and LogMeIn.

Step 2: Configure LogMeIn to support provisioning with Microsoft Entra ID

1. Log in to the Organization Center.

2. The domain used in your account's email address is the domain that you are prompted to verify within 10 days.

3. You can verify ownership of your domain using either of the following methods:

   Method 1: Add a DNS record to your domain zone file.
   To use the DNS method, you place a DNS record at the level of the email domain within your DNS zone. Examples using "main.com" as the domain would resemble: @ IN TXT "logmein-verification-code=00aa00aa-bb11-cc22-dd33-44ee44ee44ee" OR main.com. IN TXT “logmein-verification-code=00aa00aa-bb11-cc22-dd33-44ee44ee44ee”

   Detailed instructions are as follows:

   1. Sign in to your domain's account at your domain host.
   2. Navigate to the page for updating your domain's DNS records.
   3. Locate the TXT records for your domain, then add a TXT record for the domain and for each subdomain.
   4. Save all changes.
   5. You can verify that the change has taken place by opening a command line and entering one of the following commands below (based on your operating system, with "main.com" as the domain example):
      • For Unix and Linux systems: $ dig TXT main.com
      • For Windows systems: c:\ > nslookup -type=TXT main.com
   6. The response will display on its own line.

   Method 2: Upload a web server file to the specific website. Upload a plain-text file to your web server root containing a verification string without any blank spaces or special characters outside of the string.

   • Location: http://<yourdomain>/logmein-verification-code.txt
   • Contents: logmein-verification-code=00aa00aa-bb11-cc22-dd33-44ee44ee44ee

4. Once you have added the DNS record or TXT file, return to Organization Center and click Verify.

5. You have now created an organization in the Organization Center by verifying your domain, and the account used during this verification process is now the organization admin.

Step 3: Add LogMeIn from the Microsoft Entra application gallery

Add LogMeIn from the Microsoft Entra application gallery to start managing provisioning to LogMeIn. If you have previously setup LogMeIn for SSO, you can use the same application. However it is recommended that you create a separate app when testing out the integration initially. Learn more about adding an application from the gallery here.

Step 4: Define who will be in scope for provisioning

The Microsoft Entra provisioning service allows you to scope who will be provisioned based on assignment to the application and or based on attributes of the user / group. If you choose to scope who will be provisioned to your app based on assignment, you can use the following steps to assign users and groups to the application. If you choose to scope who will be provisioned based solely on attributes of the user or group, you can use a scoping filter as described here.

• Start small. Test with a small set of users and groups before rolling out to everyone. When scope for provisioning is set to assigned users and groups, you can control this by assigning one or two users or groups to the app. When scope is set to all users and groups, you can specify an attribute based scoping filter.

• If you need additional roles, you can update the application manifest to add new roles.

Step 5: Configure automatic user provisioning to LogMeIn

This section guides you through the steps to configure the Microsoft Entra provisioning service to create, update, and disable users and/or groups in TestApp based on user and/or group assignments in Microsoft Entra ID.

To configure automatic user provisioning for LogMeIn in Microsoft Entra ID:

1. Sign in to the Microsoft Entra admin center as at least a Cloud Application Administrator.

2. Browse to Identity > Applications > Enterprise applications

   

3. In the applications list, select LogMeIn.

   

4. Select the Provisioning tab.

   

5. Set the Provisioning Mode to Automatic.

   

6. Under the Admin Credentials section, click on Authorize. You will be redirected to LogMeIn's authorization page. Input your LogMeIn username and click on the Next button. Input your LogMeIn password and click on the Sign In button. Click Test Connection to ensure Microsoft Entra ID can connect to LogMeIn. If the connection fails, ensure your LogMeIn account has Admin permissions and try again.

   

   

   

7. In the Notification Email field, enter the email address of a person or group who should receive the provisioning error notifications and select the Send an email notification when a failure occurs check box.

   

8. Select Save.

9. Under the Mappings section, select Synchronize Microsoft Entra users to LogMeIn.

10. Review the user attributes that are synchronized from Microsoft Entra ID to LogMeIn in the Attribute-Mapping section. The attributes selected as Matching properties are used to match the user accounts in LogMeIn for update operations. If you choose to change the matching target attribute, you will need to ensure that the LogMeIn API supports filtering users based on that attribute. Select the Save button to commit any changes.

    Attribute	Type
    userName	String
    externalId	String
    active	Boolean
    name.givenName	String
    name.familyName	String
    urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:department	String
    urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:employeeNumber	String
    urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:costCenter	String
    urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:division	String

11. Under the Mappings section, select Synchronize Microsoft Entra groups to LogMeIn.

12. Review the group attributes that are synchronized from Microsoft Entra ID to LogMeIn in the Attribute-Mapping section. The attributes selected as Matching properties are used to match the groups in LogMeIn for update operations. Select the Save button to commit any changes.

    Attribute	Type
    displayName	String
    externalId	String
    members	Reference

13. To configure scoping filters, refer to the following instructions provided in the Scoping filter tutorial.

14. To enable the Microsoft Entra provisioning service for LogMeIn, change the Provisioning Status to On in the Settings section.

    

15. Define the users and/or groups that you would like to provision to LogMeIn by choosing the desired values in Scope in the Settings section.

    

16. When you are ready to provision, click Save.

    

This operation starts the initial synchronization cycle of all users and groups defined in Scope in the Settings section. The initial cycle takes longer to perform than subsequent cycles, which occur approximately every 40 minutes as long as the Microsoft Entra provisioning service is running.

Step 6: Monitor your deployment

Once you've configured provisioning, use the following resources to monitor your deployment:

1. Use the provisioning logs to determine which users have been provisioned successfully or unsuccessfully
2. Check the progress bar to see the status of the provisioning cycle and how close it is to completion
3. If the provisioning configuration seems to be in an unhealthy state, the application will go into quarantine. Learn more about quarantine states here.

Additional resources

• Managing user account provisioning for Enterprise Apps
• What is application access and single sign-on with Microsoft Entra ID?

Next steps

• Learn how to review logs and get reports on provisioning activity