Hello ​@MarioMC,

Thank you for reaching out, and welcome to the Docusign Community! We appreciate your question and want to assure you that we are fully committed to providing you with the best service possible. 

I understand you are getting an 'App is not set up' error when opening the Docusign for Intune application. I sincerely apologize for the inconvenience this has caused you. 

The error message means the app protection policies have not yet been assigned to the application.  While App Protection Policies were applied to "All Apps,” it appears that the Docusign Intune is not included.

If the Docusign Intune app shows no results, please try to find the Docusign app search within the Intune environment using the bundle ID: com.docusign.DocuSignIt.MDMIntune

Also, Microsoft added a new way to add App Store apps using its Web link: https://apps.apple.com/us/app/docusign-for-intune/id6636465393.
Steps: Create app > Web-link > Fill out the App Information and add the App URL:  https://apps.apple.com/us/app/docusign-for-intune/id6636465393

Next is to create and assign an app protection policy following the steps outlined here: Create and assign an app protection policy - Microsoft Intune | Microsoft Learn

Please note that this is not a product developed by Docusign, so if this recommendation does not work, kindly contact Microsoft for investigation.

Let us know if you need further assistance.

Best regards,

Melanie | Docusign Community Moderator

"Select as Best" below if you find the answer a valid solution to your issue.

thx for your answer.

that works, I was able to add the app to the app protection polcies as a custom app.

But I still have problems to configure the app correctly. is there any documentation about the keys that can be used to configure the app? like the ones mentioned in this post:

where can I found info about them?

I tried those ones and they don’t work

thx in advance

Hello ​@MarioMC,

I hope you are doing well.

The best way is to open a case with Support: Open a case in the Docusign Support Center. However, I see that you are already communicating this with one of our dedicated support team members. They are the correct team to best assist you with your questions.

I am hoping for positive results.

Let us know if you need further assistance. Thank you!

Best regards,

Melanie | Docusign Community Moderator

"Select as Best" below if you find the answer a valid solution to your issue.

thanks for your reply Melanie.

I did open a ticket with support, escalated to Docusign engineering team and they found the issue. created a and released a new version of Docusign for Intune which works perfectly.

the appConfig keys are well passed on to the app and applied to prepopulate the username, also the tenant to skip the DS login screen and the authentication works as it should.

a very good support.

Hello ​@MarioMC,

That's fantastic news! I appreciate the update. Our support team cannot do this without you!

Favor, can you kindly select your answer as best? It will help other community members who might have similar questions. 

Thank you!

Best regards,

Melanie | Docusign Community Moderator

"Select as Best" below if you find the answer a valid solution to your issue.

Hey ​@MarioMC,
did you find any documentation about the appConfig keys required for the App to work?

BR

Alex

hi ​@Alex FNMZ , I thought they had sent me a link to the doc with the keys but I cannot find it now.

I requested it again and I’ll post it here when received. in the meantime, here is what I did:

CompanyLoginDomain    String    {{UserPrincipalName}}
TenantName    String    �CompanyName as appearing in Docusign license]
EmbeddedBrowserLogin    String    { enableEmbeddedBrowserLogin: true, allowListDomains: r “whateverYouNeedToAllow” ] }
The keys are valid for both versions of the app.
We found out we cannot use the standard version due to the problems allowing file exfiltration, so we blocked the standard version in our environment.

Just the first 2 are needed in our setup for the intune version.
They were not working initially, but after a ticket with DS support, they reckoned the issues for the AppConfig keys to be passed on to the DS for intune version, and the authentication problem, then within a week they released a new version to correct both issues.

The 3rd key above needs to be used if you want to authenticate in the app embedded browser and use WkWebkitview instead Safari (but doing that prevents the app from using the certificates stored in the device keychain, so not good if you are using cert based auth for the mobile devices.
 

I forgot, to have a correct app protection policy applied, on top of the Docusign specific keys mentioned above I also deployed the following keys, same as for the other apps using AppProtectionPolicies:

IntuneMAMUPN           String     {{userprincipalname}}
IntuneMAMOID            String     {{userid}}
IntuneMAMDeviceID    String     {{deviceID}}
IntuneMAMRequireAccounts  String   Enabled
IntuneMAMAllowedAccountsOnly  String   Enabled

hi ​@Alex FNMZ , I requested the link again but the doc is not available publically for now. if you open a request with the support they will send it to you.

I attached the file here below, so you or anybody else can access it.