Update pipeline problems about intunecd HOT 16 CLOSED

Do I understand correctly you are not getting this error if you run the update towards the same environment locally?

from intunecd.

Can you try to do a new backup of the Windows Enrollment profiles in the repo and run the update after that?

For one specific Windows Enrollment profile in Intune it is not able to get the ID for some reason

from intunecd.

Yeah, If I run it's locally on same env there is no any errors at all. Already tried that and it's not working.

from intunecd.

Can you share the YAML of the pipeline used?

from intunecd.

Sure, here it is:

`trigger:
branches:
include:
- main

pool:
vmImage: ubuntu-latest

variables:
REPO_DIR: $(Build.SourcesDirectory)/git-backup-update-test

steps:

• checkout: self
  persistCredentials: true

• script: pip3 install IntuneCD
  displayName: Install IntuneCD

• script: IntuneCD-startupdate -m 1
  env:
  REPO_DIR: $(REPO_DIR)
  TENANT_NAME: $(TENANT_NAME)
  CLIENT_ID: $(CLIENT_ID)
  CLIENT_SECRET: $(CLIENT_SECRET)
  displayName: Run update`

from intunecd.

Thanks, are you able to narrow down which enrollment profile it throws the error on?

from intunecd.

Nope, it's not showing which one is making problems, we are just having two enrollment profiles and as i mentioned it was working like couple of days ago, there was not any change in those profiles.

from intunecd.

Can you double check that there is no duplication of the enrollment profiles in the repo, for example the same config is saved in both YAML and JSON?

from intunecd.

Already checked that couple of times, even done backup to new folder to have everything fresh and than tried update from new folder and still failing on same profile, there is no double config....

from intunecd.

I'm really struggling to replicate this, especially since it is working from your machine locally. I cannot see that the fault would be in the tool in that case.

This is probably the last thing you want to do but can you try to create a new project in Azure DevOps with fresh new pipelines and check if you still have the same issue?

from intunecd.

Done that, everything was fresh still failing on the same policy.

from intunecd.

I think I'm able to replicate this now. I will run some tests tomorrow and update here!

from intunecd.

Version 1.3.4 has been released (#94) and includes bug fixes for the Windows Enrollment profile issue where it exits with KeyError: 'id'.

from intunecd.

I will keep this issue open until it is confirmed it is working for you @Nikolara97 😊

from intunecd.

from intunecd.

Fantastic, thanks for confirming :)

from intunecd.