microsoftgraph / microsoftgraph/msgraph-metadata

Update-MgPrivilegedAccessResourceRoleSetting - error URI api.azrbac.mspim.azure.com

Open
#233 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

metadata-issue
Dominant language
XSLT
Stars
166
Forks
55
Avg merge
16h 12m
Merged PRs (30d)
14

Description

Hi,
I have an issue with the cmdlet Update-MgPrivilegedAccessResourceRoleSetting.
I try Update-MgPrivilegedAccessResourceRoleSetting -PrivilegedAccessId azureResources -GovernanceResourceId $RoleSetting.ResourceId -GovernanceRoleSettingId $RoleSetting.Id
I am sure the IDs are correct.
But the response is :

Absolute Uri:
https://graph.microsoft.com/beta/privilegedAccess/azureResources/resources/********-****-****-****-************/roleSettings/********-****-****-****-************

Followed by :

Body:
{
  "error": {
    "code": "UnknownError",
    "message": "{\"message\":\"No HTTP resource was found that matches the request URI 'https://api.azrbac.mspim.azure.com/api/v2/governanceResources('********-****-****-****-************')/roleSettings('********-****-****-****-************')?'.\"}",
    "innerError": {
      "date": "2022-12-16T21:00:48",
      "request-id": "5fb90750-367b-4976-8913-659c5b5863ba",
      "client-request-id": "5fb90750-367b-4976-8913-659c5b5863ba"
    }
  }
}

What can I do to resolve this issue ?
Thanks !
Vincent.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing Update-MgPrivilegedAccessResourceRoleSetting from the Microsoft Graph beta URI to the reported api.azrbac.mspim.azure.com route and checking the metadata or endpoint mapping. Done means identifying the supported request shape or documenting the service-side mismatch; the issue names no repository file or test to run.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, powershell
Domain
api, cloud
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.