Delegated authentication

With delegated authentication, Printix uploads each scan as the user who made it, using the Microsoft account and privileges of that user. Delegated authentication is available only for Microsoft OneDrive and Microsoft SharePoint Online destination profiles.

You select the authentication type for each destination profile. For delegated authentication, select Delegate the access grant to end-users in Authentication Type. To compare delegated authentication with a shared service account, see Comparison with a service account.

Access control and audit benefits

  • Documents in Microsoft 365 are attributed to the person who scanned them, not to the Printix application, so the audit trail identifies the person who made the scan.

  • Printix does not need privileges to write to the files of every user. Each user grants their own access.

  • Printix writes files only where the account of the scanning user already has privileges.

  • Delegated authentication is suitable for organizations whose security policy does not allow tenant-wide application access to OneDrive or SharePoint.

Comparison with a service account

Service account Delegated
The file is written as One shared Printix identity, on behalf of the scanning user. The user who made the scan.
The scanning user must Do nothing. Connect their Microsoft account once, the first time they scan to the destination.
Microsoft grants Application privileges to the files of all users. Delegated privileges, limited to what the user can already access.
Access stops working when The consent is withdrawn in Microsoft Entra ID. Microsoft access for the user is removed or expires. The next scan waits, and Printix asks the user to connect again.

Microsoft Entra ID privileges

Your security team must approve these privileges for delegated access.

Cloud service Delegated privileges Administrator consent needed
Microsoft OneDrive Files.ReadWrite: only the files of the signed-in user. Yes, once per Microsoft Entra directory.
Microsoft SharePoint Online Sites.ReadWrite.All: limited to the sites and libraries the signed-in user can already access. Yes, once per Microsoft Entra directory.

The delegated SharePoint privileges have the same name as the application privileges, but they can never grant more access than the individual user already has in SharePoint. The application privileges are not limited by what the individual user can access. The Microsoft consent screen does not show this difference.

The user experience

  • The first time a user scans to a delegated destination, the scan waits, and the user receives an email with the subject "Your scan is waiting for your permission". The scan is not discarded.

    • The printer shows nothing different, and the scan appears to complete. Only the email notifies the user that the scan is waiting.

    • On the History page, the scan appears as started. No further entry appears until the user connects their account.

  • In the email, the user selects Grant permission, which opens a page where they connect their Microsoft account. Microsoft does not ask them to allow anything, because the administrator consent already covers the access.

  • Printix then delivers the waiting scan. The user does not have to scan again.

  • Later scans need no action.

  • If Microsoft access for the user is removed or expires, the next scan waits, and Printix emails the user again.

  • Users can also grant access in advance on the "Cards, codes and access" page in the Printix App.

Limitations

  • The user must sign in to Microsoft with the email address they use for Printix.

    Printix matches the email address against the Microsoft account mail address or user principal name. If neither address matches, the user cannot connect their account and receives a message that the account does not match. Align the addresses in Microsoft Entra ID before you use delegated destinations.

  • Users who are not in the directory cannot use delegated destinations.

    A workflow that sends to a delegated destination profile is offered only to users who are members of the Microsoft Entra directory for that destination. Users who sign in with an email address and password are not members of a Microsoft Entra directory, so they do not see the workflow at the printer or in the Printix App.

  • A scan waits up to 24 hours.

    If the user does not grant access within 24 hours, the scan fails and Printix discards the document. On the History page, the scan appears as a delivery timeout. The user must scan again. The email does not mention this time limit, so tell your users to act on the email promptly.

  • Withdrawing consent applies to a whole Microsoft Entra directory, never to one user.

    Users and administrators cannot remove access for an individual user. After a user connects their account, the entry on the "Cards, codes and access" page offers no action. Access for an individual user ends only when their Microsoft access is removed or expires.

    Withdrawing consent for a Microsoft Entra directory clears the administrator consent and deletes the stored access grant for every user in that directory. Those users must connect their Microsoft accounts again the next time they scan. No page offers this.