If you've deployed an Azure VM and did not enable the “Login with AAD credentials”, option, you can enable sign in using Azure Active Directory credentials later using Cloud Shell with this command in Azure CLI:
az vm extension set \
--publisher Microsoft.Azure.ActiveDirectory \
--name AADLoginForWindows \
--resource-group ResourceGroup \
After running that command, you'll need to add an entry to the local group to allow interactive sign in using RDP. The extension doesn't add this permission and you will need to do it manually, running this command in a remote Powershell:
net localgroup "remote desktop users" /add "AzureAD\firstname.lastname@example.org"
You will also need to add 2 lines the RDP file downloaded from the “Connect” tab so that you can connect without issues:
After connecting to the VM using RDP, you will also need to disable network-level authentication from Control Panel.
In the background, the extension will change the Join Type of the VM to “Azure AD Joined” and your Devices blade will update with that information after a couple of minutes.
The Freshservice Discovery Agent helps you keep track of your assets by sending details (and updates) about the machine it is installed on. You can use Microsoft Endpoint/Intune to deploy the Discovery Agent in all the computers in your tenant.
Download Discovery Agent
In Freshservice, go to Admin –> Discovery
In the Download Agent section, choose Windows. Click the Download Agent button.
Click All apps in the menu and then click on the Add button.
Choose Windows app (Win32) in the dropdown menu for App type and then click the Select button to continue.
In the first page of the wizard, click the link Select app package file. Find the .intunewin package and click the OK button to begin uploading.
Back on the “Add information” tab, put in the required information and click the Next button to continue.
On the “Program” tab, don't change any of the default options. Click the Next button.
On the “Requirements” tab, change the two required options. Click the Next button.
For “Operating system architecture”, select both 32 bit and 64 bit.
For “Minimum operating system”, select the lowest value. In this case, it's Windows 10 1607.
On the “Detection rule” tab, change the “Rules format” dropdown to “Manually configure detection rules.” Click the link to Add a new rule. In the popup pane, change the “Rule type” to “MSI” and the MSI product code should automatically generate the correct number. Click the OK button to continue and then Next.
On the “Dependencies” tab, just leave default and click the Next button.
On the “Assignments” tab, select the groups in the Required category on which you want the Freshservice Discovery tool to be installed. Click the Next button.
On the “Review + create” tab, make sure the options look correct and then click the Create button.
Remain on the page for a few minutes while the package uploads. When it's finished uploading and processing, the assignments will be populated and computers in the group will begin to receive the deployment.