PR: IntuneDeviceConfigurationEditionUpgradePolicyWindows10 - Repost

[William-Francillette]

Pull Request (PR) description

This Pull Request (PR) fixes the following issues

• IntuneDeviceConfigurationEditionUpgradePolicyWindows10
• Initial release

Please put on hold until issue resolved with SDK cmdlet:
microsoftgraph/msgraph-sdk-powershell#1930

Also the Intune portal obfuscate the productKey parameter so I am only testing the last 4 digits in Test-TargetResource and remove the parameter in Set-TargetResource when obfuscated

[William-Francillette]

@NikCharlebois Can we put this one on hold until the SDK is fixed?

[ykuijs]

@William-Francillette Do you have an update on this? I see that the SDK issue has been closed. Does that mean the issue is now fixed?

[William-Francillette]

@ykuijs, I will test the resource tonight and come back to you

[William-Francillette]

@ykuijs @NikCharlebois Unfortunately this is not fixed, there is an issue with the API and not the SDK.
The policy is updated during the configuration but the response is empty and thus raise an error.
Same issue using the REST API or SDK.

I have raised a ticket from my Azure subscription 2306130050004983

Can you guys escalate that?

Thanks

[William-Francillette]

@ykuijs @NikCharlebois - That Azure ticket is not leading to anything - I had a call with the support engineer last week and he told be my ticket was bounced for more than 2 weeks between the Intune and Graph team

Can you guys escalate it?

[andikrueger]

@William-Francillette just to clarify: is this issue resolve by now or did you find a workaround?

[William-Francillette]

Nope it isnt , I'll check again with the v2.0 but it may not help as it is an api issue rather than the sdk

[andikrueger]

Is there any issue within this repository that holds information about the issue? Right now it’s (was) just the PR, right? It would be good to track it somewhere

[William-Francillette]

Oh I've just realised I've closed the PR !
I was cleaning up my repo and removed all my intune branches but completely forgot that one.

Ill generate it again and repost it

Silly me!

[FabienTschanz]

@William-Francillette Just stumbled upon this pull request as I was having a look at those edition upgrades myself. Do you have any new hints on the case?

In my opinion, this seems to be related to the service behind the creation of the resource sending an error back when the action is not performed by an "interactive" user. I analyzed the JWT-Token sent by the Intune console and the one sent by the Graph PowerShell command, but nothing out of the ordinary that should raise a red flag... Maybe we should just deal with the error (meaning catch and work around it)? Or can we somehow push the team(s) to fix their service eventually? That issue is now very old...

[William-Francillette]

I would guess this issue won't be resolved anytime soon as configurationprofiles aren't really developed anymore afaik.
There is an issue with the API and it's not related to the SDK. Unfortunately, I've never been able to get help on that one, my ticket was passed from a support team to another without any progress.
Not sure best course of action here