Many customer support cases for EPM that involve Azure AD are not related to EPM. For example, some customers use Azure AD or groups in advanced policy targeting, but the end-user is not logged in with an Azure AD user. The purpose of the article is to provide a few commands to use as troubleshooting steps to gather information and possibly show if issues are outside of EPM or not.
Steps
Advanced Policy Targeting
Check userdomain variable
Run this from cmd
echo %userdomain%
expected outcome: Should see AzureAD If you see something else, the user may be logged in with a regular active directory user
Check whoami output
Run this from cmd
whoami /all
Expect to see azuread\username Expect to see "NT AUTHORITY\Cloud Account Authentication" If you don't see the above, it might be an indication that the user may be logged in with a regular active directory user Note: May not see the actual Azure AD groups listed
Testing if the computer/user can talk to AzureAD
Run the powershell commands
$path = "C:\myfolder" $permission = "AzureAD\
[email protected]","FullControl","Allow" (Get-Acl $path).SetAccessRule((New-Object System.Security.AccessControl.FileSystemAccessRule $permission)) | Set-Acl $path
Expected outcome: It should set the security permission on the folder
AzureAD authentication
Test if the computer can authenticate to AzureAD (outside of EPM)
On the endpoint, run "C:\Program Files\CyberArk\Endpoint Privilege Manager\agent\vf_agent.exe" -SuspendPolicies Enter credentials of someone who can suspend policies Open file explorer and browse to c:\windows\system32 shift+right click notepad.exe > open as different user Enter user in form of azuread\
[email protected] Enter credentials and see if notepad opens. If not, the endpoint may have a problem reading the AzureAD directory, and the issue is not related to EPM. On the endpoint, run "C:\Program Files\CyberArk\Endpoint Privilege Manager\agent\vf_agent.exe" -ResumePolicies
If the customer can't authenticated to AzureAD using the above step, it is not expected that they should be able to suspend policies using an Azure AD user