Skip to main content
UdaM
UdaM
Explorer III
February 13, 2026
Solved

FortiSASE User group import from local AD ( Windows) via Radius

  • February 13, 2026
  • 2 replies
  • 199 views

Hi All

 

We have successfully integrated with RADIUS, and all user authentications are working fine. However, we need to import user groups from Active Directory into FortiSASE users and groups.

The RADIUS Group ID value is required for this. Could you please let us know where we can find this value?

 

Screenshot 2026-02-13 082845.png

 

 

Thankz

 

Best answer by UdaM

Dear @tbarua @Stephen_G 

 

The issue has been resolved by configuring a Vendor-Specific Attribute (VSA) on the AD NPS server. The group name is now correctly received from Active Directory.

 

https://docs.fortinet.com/document/fortigate/7.6.3/administration-guide/952303/radius-avps-and-vsas?utm_source=chatgpt.com

 

https://learn.microsoft.com/en-us/azure/virtual-wan/user-groups-radius?utm_source=chatgpt.com

 

Thank you

2 replies

Stephen_G
Moderator
Stephen_G
Moderator
February 16, 2026

Hello Udara_CM,

 

Thank you for using the Community Forum. I will seek to get you an answer or help. We will reply to this thread with an update as soon as possible. 

 

If anybody else has any info or advice, please feel free to contribute!

Regards,
Stephen_G - Fortinet Community Team
tbarua
Staff
tbarua
Staff
February 16, 2026

Hello Udara_CM,

The group id is the specified name in the RADIUS server : 

Please find the docs as an example:

https://community.fortinet.com/t5/FortiSASE/Troubleshooting-Tip-FortiSASE-Policy-Enforcement-Not-Working-for/ta-p/405465

https://docs.fortinet.com/document/fortisase/latest/mature-administration-guide/877752/configuring-fortisase-with-a-radius-server-for-remote-user-authentication

 

 

    UdaM
    UdaMAuthor
    Explorer III
    February 16, 2026

    Dear @tbarua @Stephen_G 

     

    Appreciate your effort...

     

    I'll check this and let you know the results. 

     

    Thank you.

    Terms & ConditionsAccessibility statement