Update to Microsoft Intune PowerShell example script repository on GitHub

Hi all,

Thank you for all the comments sharing your feedback, experience, and questions in regards to this feature. As mentioned in the article, we will continue to work to add additional script samples will in the future, and if you have any suggestions for changes, updates, or ideas for new samples, continue to share them in the comments below or reach out to us on Twitter @IntuneSuppTeam. 

If we have missed any of your comments, and you continue to experience issues, please reach out to us via DM so we can investigate further.

Thanks!

I am baffeled by the way this upgrade is communicated.

After about 8 browsertabs I still am just able to find partial information, with texts like "Select the checkbox next to the required permissions", but without mentioning the required permissions. Just share the one-stop-shop persmissionset to fully enable the functionalities within this module...

As far as comments in this thread go I believe I am not the only one.

However, if I understand correctly, we now end up with a module where each time the app id should be updated when you administer multiple Microsoft tenants, since you cannot choose the app id that will be created.

"With the theme of simplification" it might help to create a comprehensive setup-guide and an easy workaround to connect to multiple tenants.

For anyone lost in how to properly upgrade or create a new app registration:
powershell-intune-samples/Updating App Registration at master · microsoftgraph/powershell-intune-samples · GitHub

Tip 2: Do not use the wildcards in the return url. It's just urn:ietf:wg:oauth:2.0:oob

Hopefully this will be adressed, so that connecting to an environment becomes easier. Other modules are able to request a new registration if needed, while giving consent during authentication.

Hello everyone, my script “IntuneWin32” unfortunately requires the Connect-MSIntuneGraph connection. However, I only get errors here. Does anyone have an idea?

Guys,

We have peace of code like this:

Update-MSGraphEnvironment -AppId "e00ac69e-........"

$cred = Get-Credential

connect-msgraph -Credential $cred

if we store those creds somewhere or use it like this we are getting following error:

connect-msgraph : AADSTS7000218: The request body must contain the following parameter: 'client_assertion' or 'client_secret'. Trace ID: 45bee449-0fe5-4cf3-9aa1-c52277731b00 Correlation ID: 4e795f88-745a-4c30-9363-f3f25ae18c14 Timestamp: 2024-05-16 13:55:08Z
At line:1 char:1

connect-msgraph -Credential $cred
+ CategoryInfo : NotSpecified: (:) [Connect-MSGraph], AdalServiceException
+ FullyQualifiedErrorId : Microsoft.IdentityModel.Clients.ActiveDirectory.AdalServiceException,Microsoft.Intune.PowerShellGraphSDK.PowerShellCmdlets.Connect

However if we just run connect-msgraph and type creds in Azure windows that pop-ups script executes without issue but we need to store those creds so script can execute without our interaction...

Any idea how to solve this?

BR

Hello ,
I use the Win32App script to package and upload Intune applications.
I have installed it as follows. But then I get the following:

The simple connection with Connect-MSIntuneGraph does not work either. It looks as if the old app ID is still stored?
Connect-MSIntuneGraph -TenantID xxxxxxxxxxxxxxxxxx

Hello.  I added this to my script (which handled Intune MDM device management), prior to the Connect-MsGraph cmdlet:

Update-MsGraphEnvironment -AppID <MY-NEWLY-REGISTERED-APP-ID> | Out-Null

Hello everyone,

I have also registered and authorized the new Enterprise App as described in the instructions. I have also updated the environment.

Unfortunately, the script still calls up the old app. What have I overlooked?

Connect-MSIntuneGraph -TenantID "xxxxx.onmicrosoft.com"

nhtkid I struggled with this for a few days, but I think I have now figured it out.  

I used option #2 (Register app in Entra ID and give Intune Graph permission in it) from this documentation:  

https://github.com/microsoftgraph/powershell-intune-samples/blob/master/Updating%20App%20Registration

Once the Enterprise App was fully created, I ran this command in PowerShell:

Update-MSGraphEnvironment -appid <MY_NEW_APP_ID#>

Then I was able to connect with 

Connect-MsGraph

and it no longer gave an error.

I am now able to run my old/traditional commands such as

Get-IntuneManagedDevice

So I have this simple script that could sync or reboot Intune devices.

It stopped working now due to the application id (d1ddf0e4-d672-4dae-b554-9d5bdfd93547) being retired.

I have many other scripts performing different Intune related tasks but all utilising MsGraph.

What exactly do I need to update to make the script working again?

Thanks!

Connect-MSGraph
$DeviceGroup = Read-Host -Prompt "Please provide the AAD group object ID"

$DeviceList = Get-Groups_Members -groupId $DeviceGroup -Select id, deviceId, displayName | get-MSGraphAllpages

$AllIntuneDevices = Get-IntuneManagedDevice -select id, operatingSystem, azureADDeviceId -Filter "contains(operatingSystem, 'iOS')" | get-MSGraphAllpages

foreach ($Device in $DeviceList)

{
    $deviceIntuneId = $AllIntuneDevices | Where-Object {$_.azureADDeviceId -eq $Device.deviceId}

    Write-Host $Device.deviceId

    if($deviceIntuneId)
    {
        Invoke-DeviceManagement_ManagedDevices_SyncDevice -managementDeviceId $deviceIntuneID.id

        Write-Host "Sync command has been sent to the device"
    }

    else {
        Write-Host "$Device.deviceId not found"
    }

}