This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(57.599999999999994, 52%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
When trying to assign Machine Configuration in the ARC machine portal GUI it always fails with a ResourceNotFound error.
I guess it is because, when creating Machine Configuration, it always uses Microsoft.Compute/virtualMachines instead of Microsoft.HybridCompute/machines in the JSON template type key.
I think this is the problem, because if I manually customize the JSON template to look like this
And deploy it as a custom template, it works and policy gets assigned to the device.
Same goes when creating such assignment via "Guest Assignment" portal.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(275.2, 41%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAM%3C/text%3E%3C/svg%3E)
@Andrew, thank you for posting this question on Q&A.
All the screenshots attached with the thread are missing. Could you please attach them again.
I am sorry, I could not understand the question. Could you please share the steps that you are following (or relevant document) to he me understand the issue better.
Edited
@Andrew, thank you for the clarification. I tested and I was able to see similar behavior. I am reaching out to the team to get more details and will update this thread.
Any news?
@Andrew, The Azure Arc team is reviewing this issue. I will share further updates as I have them. Thank you very much for reaching out.
@Andrew, thank you again for bringing this issue to our attention.
The Azure Arc team is investigating this issue. We dont have a specific timeline for it to be fixed yet. I will share further updates as I have.