Filter › Filter Deployment
Deploying SmartPAC with Microsoft Intune
This article provides specifics on how to deploy standard SmartPAC with InTune and some notes about the User_Injection feature.
*It should be noted that Intune is in a state of rapid development and these screenshots and menu's are subject to change.*
Step 1 - Access the Microsoft Endpoint Manager and admin center intune.microsoft.com
Step 2 - The SmartPAC specific setting is located under Devices - Windows-Configuration -Create new policy-select platform Windows 10 or later, profile type is template - select Device Restrictions -then create
Step 3- Under configuration settings, click network proxy and use your custom SmartPac URL.
**NOTE: We've identified a bug in Intune: you have to allow and then click not configured under "manual proxy server" to continue
*Just as with MDM deployments and AD GPO you will as well need to deploy the Securly certificate to your Intune controlled devices.*
On the topic of User_Injection and Intune
If you have reached this article and don't quite know what User_Injection is please consult the following KB article first:
/docs?article=360041375734>
Since User_Injection utilizes variables to assist SmartPAC in grabbing usernames this does not currently work by default in Intune. This is because Intune deploys the SmartPAC to the browser directly and browsers do not interpret variables such as %USERNAME% or other variables in this fashion.
If you want to utilize User_Injection in your Intune environment for Windows devices SmartPAC MUST be deployed via a registry edit. Currently there is no clear and easy path for registry modification within Intune besides writing custom scripts or wrappers.
The registry entry in question:
Hive: HKEY_CURRENT_USER
Key Path: Software\Microsoft\Windows\CurrentVersion\Internet Settings
Action: Create
Value Name: AutoConfigURL
Value Type: REG_SZ
Value Data: The SmartPAC URL provided to you by Securly Support or Sales team member.
*Note that by default your SmartPAC URL may use HTTPS. Some versions of IE only support HTTP. Securly supports both so be aware that you may need to use HTTP.
Please also see:
Currently Securly cannot provide scripting assistance due to the complexity and variations of customer environments. Please consult your preferred Microsoft Representative or TAM for further support.