Marcel Gerber

Hello everyone.

I've tested the feature in 2026.2.12.0 for Windows.

The action button is available and works.

The shortcut in the context menu is missing.

I would expect to find it here also:

Best regards.

Marcel

DUO would be a nice addition :-)

@Marcel Gerber

Thanks for the feedback, sorry for the late reply.

We're taking note :)

Hello @Marc Beausejour

Thanks for your feedback.

I shortly discussed this point with our CISO and his view was that if we need to access secrets during an Internet failure, we would need TOTP.

So DUO is not going to be interesting for us because of this.

Best regards.

Marcel

Hello @Patrick Ouimet and @Emile Simard.

Thanks for your messages.

Please be aware that we need 3 URI's for it to work in 2026.2.7.0.

• User authentication: https://<dvlsfqdn>/dvls /api/external-provider-response

• Connection with service account: https://<dvlsfqdn>/dvls /api/configuration/authentication/azure/connect

• Connection with service account: https://<dvlsfqdn>/dvls/api/configuration/authentication/azure/connect-callback

Best regards.

DUO would be a nice addition :-)

Hello @Emile Simard

Tested: it needs both redirect URI's to work.

Otherwise I get this kind of response.

Cheers.

Marcel

Thanks @Emile Simard !

Let's see once we manage a successful delegated rights version if we need to URI's or not.

PS: For now, I can connect it, but not login to DVLS with it.

Marcel

Hello @Luc Fauvel

No worries, thanks for the reply.

Cheers.

Marcel

Perfect, thank you !

Hello @Hubert Mireault

We are currently running 2025.3 in PROD and testing 2026.2 in LAB.

I will check it out in the LAB.

Best regards.

Marcel

Hello @François Dubois

Any news about this topic ?

Thank you and best regards.

Marcel

Hello @Jean-Sébastien Simard

Has there been any work done on your search tool ?

I'm still unable to find the page mentioned in your first reply when searching for license server URL.

Best regards.

Marcel

Hello @Jafran Majeau

Thank you that helps.

Unfortunately it's only in the "Actions" ribbon/tab but not in the context menu quick actions.

Best regards.

Marcel

Hello @Emile Simard

Thank you for the update, which looks promising.

A few notes from my side.

Step 8 here is not very clear to me:

Is it to be repeated ? If so, in which case ? If not maybe it needs cleanup.

I think for Delegated rights, we need two different redirect URI's but I might be wrong.

This is not quite correct. If you do not add it here, the first user logging in will be required to do the Admin Consent.

I would rather add those manually, admin consent them and be done with it.

Instead of repeating 3 times "For Delegated permissions" I would add sub-steps for these 3 items and name the main step something like "For delegated permissions only do the following".

Thank you and best regards.

Marcel

Hello.

Do you have any news about this request ?

Thank you and best regards.

Marcel

Hello.

Do you have any news about this request ?

Thank you and best regards.

Marcel

Hello.

Do you have any news about this request ?

Thank you and best regards.

Marcel

Hello.

Do you have any news about this request ?

Thank you and best regards.

Marcel

Hello.

We have a issue that we would like to address.

1. Users MUST use DUO MFA.

2. Local Super Admin MUST use TOTP.

In the current setting, this cannot be enforced.

We would like to get the possibility to configure the MFA type within the access policy.

We have an open ticket about this, which I will be happy to share in private (or ask Patrick about it).

For example:

Cheers.

Marcel

Hello.

We would enjoy having the possibility to schedule a report based on tags set on entries.

Example, we would like to create an automation to synchronize some entries to a different vault, and would set a deleted tag on the destination if the source disappears. Then we could see where there is a problem with such a report. Today we need to create a separate script for such a task.

Thank you and best regards.

Marcel

Hello.

I have a suggestion to improve the MS authentication configuration documentation.

Configure Microsoft authentication with Entra ID - Devolutions Documentation

First, I would avoid jumping around between Entra ID and DVLS Server Administration.

I would show how to completely configure the application registration and then copy / paste most values from its overview.

This is obviously different for the secret for the secret configuration.

Secondly, I would show a complete example of how to configure an app registration with application permissions and one for delegated rights permissions. This because it's always tricky to follow a guide which has exceptions and small additions to avoid missing an important setting.

Thirdly, I would advise to show all app permissions required for both application permissions and delegated rights permissions:

1. Configure DVLS with application permissions

   1. delegated rights for :

      1. openid

      2. profile

      3. offline_access

   2. application permissions for :

      1. user.read

      2. user.read.all

      3. group.read.all

2. Configure DVLS with delegated rights permissions

   1. openid

   2. profile

   3. offline_access

   4. user.read

   5. user.read.all

   6. group.read.all

Last, please add additional required settings like the token "ID tokens (used for implicit and hybrid flows)" required for the application permission authentication mode.

Thank you.

Marcel

Hello Tommy.

Thank you, this was explained to me after I opened a support case.

It would be nice to find it in the documentation though.

Best regards.

Marcel

Hello.

We would like to use a separate vault with only sessions for some specific users.

In order to manage the credentials seamlessly, we aim to use the new "Linked (external vault)" feature.

I'm unable to find a description of the permissions required on the source entries (credentials) that we plan to use for this.

In this scenario, we don't want the specific users to have direct access to the source vault.

Best regards.

Marcel

Hello François.

Thank you for your feedback.

It is not a technical limitation, but a security baseline. Our group does not provide any app registration, because it would give access to all and everything, as there is no way to limit such apps to specific objects.

For this we would need a service account for which we should be able to provide username and password.

What I currently need from your side, are the following answers:

1. would you consider implementing this feature ?

2. If yes, what version and timeline would you estimate it to be released ?

Once we have these answers, we can define our follow-up actions.

Thank you for the answer about the group loading issue.

Do you have any estimation about its release date and version ?

Thank you very much.

Marcel

Hello.

Our new group allows only delegated permissions on application registrations.

We need to migrate to the group's tenant.

Would it be doable for you to add authentication through Microsoft DELEGATED permissions ?

In the meantime, we will see how we handle that. Maybe we keep our tenant longer and go with guest from the group tenant and keep the app registration in our current tenant.

Also, if the group search in the Microsoft authentication screen could be made to "search only" or load a subset of all the available groups that would be great. During our test, application permissions were added temporarily for testing, and the groups never loaded because after some minutes, it was still not completed.

Thank you and best regards.

Marcel

Hello.

I need to know how I can build up a filter.

Configuration - Devolutions Documentation

Can I somehow specify if it's in a folder of a certain name ?

Can I use wildcards ?

That would greatly help me.

Thank you and best regards.

Marcel