When I need to do that?

When integrating with Azure AD it is necessary to ensure that all print jobs delivered to Dispatcher Paragon are received under the correct user login. Customers using Azure AD are using two different approaches:

1.  Azure AD DS with secure LDAP available. 
2.  Pure Azure AD with Azure AD joined workstation.

Tip: if unsure which one is your case, think about your logon screen: if you are using your full email address, you are most likely on option 2.

Scenario 1: Azure AD DS with secure LDAP

Those customers are using managed domain and should follow standard LDAP integration documentation (LDAP Integration).

Reference: https://docs.microsoft.com/en-us/azure/active-directory-domain-services/tutorial-configure-ldaps

Scenario 2: Azure AD

Customers who abandoned traditional managed domain and are running pure Azure AD would be logging into their workstations using their Office 365 credentials (email address). Those are "Azure AD joined" workstations where user logins are treated differently than in standard managed domain environments. In this case there is LDAP Proxy for Azure AD (SWC-100) extension available via Extension Store.

Troubleshooting tips

In case customer doesn't have LDAP replication he can manually assign print job to an existing/new user in the management interface.

Customer should follow these steps: 

1. Open the management interface login window and log in.
   
   
   

2. On the Dashboard page click Reports.

3. On the Reports page, find the unassigned job. Select this job and click on the Assign icon.
   
   
   
4. In the dialog window, select Create a new user or Choose user from list.
   
   
   
5. Find and select user which you want to use to assign print job.
6. Confirm job assigning to the selected user by clicking YES.
   
   
   
7. On the Reports page, you should see the print job assigned to the selected user.
8. Selected user can print the job on printer.