Remove macOS script configuration details - #5205
Remove macOS script configuration details#5205Somesh Pathak (pathaksomesh06) wants to merge 1 commit into
Conversation
removed the below text for macOS as they are not available in Intune admin center when creating detection scripts for macOS platform- ---------------------------------------- macOS - On Settings, configure the following behavior for the Bash script: Run this script using the logged on credentials – Set this value to Yes to run the script in the context of the logged-on user. Enforce script signature check – Set this value to Yes to require a valid signature on the script. Hide script notifications on devices – Set this value to Yes to hide notifications from the script on the device. --------------------------------------------------------
|
Somesh Pathak (@pathaksomesh06) : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. Laura Newsad (@lenewsad) |
prmerger-automator
Bot
added
Change sent to author
microsoft-intune/svc
protect/subsvc
labels
|
Somesh Pathak (@pathaksomesh06) : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. Laura Newsad (@lenewsad) |
|
Learn Build status updates of commit 09fb8d4: ✅ Validation status: passed
For more details, please refer to the build report. |
There was a problem hiding this comment.
Pull request overview
Removes outdated macOS-specific configuration guidance from the custom compliance discovery script creation steps, aligning the documentation with what’s currently available in the Intune admin center UI.
Changes:
- Removed the macOS “Settings” behavior bullets that are no longer present in the Intune admin center flow.
- Updated the remaining step numbering to account for the removed macOS section.
- Adjusted indentation/formatting around the edited section.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| @@ -125,7 +121,7 @@ Before deploying your script in production, test it in an isolated environment t | |||
| - **Enforce script signature check** – For more information, see [about_Signing](/powershell/module/microsoft.powershell.core/about/about_signing?view=powershell-7.1&preserve-view=true) in the PowerShell documentation. | |||
| @@ -110,11 +110,7 @@ Before deploying your script in production, test it in an isolated environment t | |||
| 1. Sign into [Microsoft Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431) and go to **Endpoint security** > **Device compliance** > **Scripts** > **Add** > *(choose your platform)*. | |||
|
Can you review the proposed changes? Important: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
prmerger-automator
Bot
added
the
aq-pr-triaged
removed the below text for macOS as they are not available in Intune admin center when creating detection scripts for macOS platform-
macOS - On Settings, configure the following behavior for the Bash script: Run this script using the logged on credentials – Set this value to Yes to run the script in the context of the logged-on user. Enforce script signature check – Set this value to Yes to require a valid signature on the script. Hide script notifications on devices – Set this value to Yes to hide notifications from the script on the device. --------------------------------------------------------
