microsoftgraph / microsoftgraph/msgraph-metadata

Update-MgEntitlementManagementAccessPackageCatalogCustomAccessPackageWorkflowExtension - Issue

Open
#243 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

I am experiencing an issue with Update-MgEntitlementManagementAccessPackageCatalogCustomAccessPackageWorkflowExtension

I receive the error No HTTP resource was found that matches the request URI but when looking at the debug trace it tries to call a PATCH instead of PUT: https://learn.microsoft.com/en-us/graph/api/customaccesspackageworkflowextension-update?view=graph-rest-beta&tabs=http

This is my code (removed subscriptionID):

$ext=@{
    "authenticationConfiguration"=@{
                                        "resourceId"=  "5b6bb072-149a-4bf9-a783-308e41d8670c"
                                    }
    "endpointConfiguration"=@{
                                  "subscriptionId"=  "c2c1b8b8-****-****-a320-************"
                                  "logicAppWorkflowName"=  "AccessPackageApp"
                                  "resourceGroupName"=  "AZ-500_Training"
                              }
    "description"= "custext-DSC"
    "displayName"=  "custext2"
    }

Update-MgEntitlementManagementAccessPackageCatalogCustomAccessPackageWorkflowExtension `
    -AccessPackageCatalogId '7f66090e-11d2-4868-bc13-df98a327077d' `
    -CustomAccessPackageWorkflowExtensionId '65e8bcfd-c486-4c7b-9832-5ea25d398ac7' `
    -BodyParameter $ext -debug

Debug trace:
PS C:\temp\m365DSC\Backup\AADEntitlementManagementAccessPackageCatalog> 
Update-MgEntitlementManagementAccessPackageCatalogCustomAccessPackageWorkflowExtension `
    -AccessPackageCatalogId '7f66090e-11d2-4868-bc13-df98a327077d' `
    -CustomAccessPackageWorkflowExtensionId '65e8bcfd-c486-4c7b-9832-5ea25d398ac7' `
    -BodyParameter $ext -debug
DEBUG: [CmdletBeginProcessing]: - Update-MgEntitlementManagementAccessPackageCatalogCustomAccessPackageWorkflowExtension begin processing with parameterSet 'Update'.
DEBUG: [Authentication]: - AuthType: 'AppOnly', AuthProviderType: 'ClientCredentialProvider', ContextScope: 'Process', AppName: 'Microsoft365DSC'.
DEBUG: [Authentication]: - Scopes: [Agreement.ReadWrite.All, TeamSettings.ReadWrite.All, TeamMember.Read.All, Policy.Read.ConditionalAccess, DeviceManagementManagedDevices.Read.All, Device.Read.All, Po
licy.ReadWrite.ConditionalAccess, TeamsTab.Read.All, TeamsActivity.Read.All, TeamMember.ReadWriteNonOwnerRole.All, Device.ReadWrite.All, User.ReadWrite.All, TeamsTab.Create, RoleManagement.Read.Directo
ry, Policy.ReadWrite.ApplicationConfiguration, Application.ReadWrite.All, Group.Read.All, TeamworkDevice.ReadWrite.All, Directory.ReadWrite.All, TeamsActivity.Send, TeamsTab.ReadWrite.All, MailboxSetti
ngs.Read, DeviceManagementServiceConfig.Read.All, Team.Create, Group.ReadWrite.All, Directory.Read.All, User.Read.All, Agreement.Read.All, Tasks.Read.All, DeviceManagementServiceConfig.ReadWrite.All, G
roupMember.Read.All, TeamMember.ReadWrite.All, Organization.ReadWrite.All, DeviceManagementConfiguration.Read.All, Team.ReadBasic.All, Mail.Read, DeviceManagementManagedDevices.ReadWrite.All, TeamSetti
ngs.Read.All, User.ManageIdentities.All, Organization.Read.All, RoleManagement.ReadWrite.Directory, GroupMember.ReadWrite.All, Tasks.ReadWrite.All, Policy.Read.All, DeviceManagementConfiguration.ReadWr
ite.All, Application.Read.All, DeviceManagementApps.ReadWrite.All, DeviceManagementApps.Read.All, TeamworkDevice.Read.All, AgreementAcceptance.Read.All].
DEBUG: ============================ HTTP REQUEST ============================

HTTP Method:
PATCH

Absolute Uri:
https://graph.microsoft.com/beta/identityGovernance/entitlementManagement/accessPackageCatalogs/7f66090e-11d2-4868-bc13-df98a327077d/customAccessPackageWorkflowExtensions/65e8bcfd-c486-4c7b-9832-5ea25d
398ac7

Headers:


Body:
{
  "description": "custext-DSC",
  "authenticationConfiguration": {
    "resourceId": "5b6bb072-149a-4bf9-a783-308e41d8670c"
  },
  "displayName": "custext2",
  "endpointConfiguration": {
    "subscriptionId": "c2c1b8b8-****-****-a320-************",
    "logicAppWorkflowName": "AccessPackageApp",
    "resourceGroupName": "AZ-500_Training"
  }
}


DEBUG: ============================ HTTP RESPONSE ============================

Status Code:
NotFound

Headers:
Transfer-Encoding             : chunked
Vary                          : Accept-Encoding
Strict-Transport-Security     : max-age=31536000
request-id                    : 7605d105-7ebc-4378-9374-02526c9489ac
client-request-id             : 7605d105-7ebc-4378-9374-02526c9489ac
x-ms-ags-diagnostic           : {"ServerInfo":{"DataCenter":"UK South","Slice":"E","Ring":"3","ScaleUnit":"000","RoleInstance":"LN2PEPF000066A3"}}
Link                          : <https://developer.microsoft-tst.com/en-us/graph/changes?$filterby=beta,PrivatePreview:AADLCM&from=2022-05-01&to=2022-06-01>;rel="deprecation";type="text/html"
Deprecation                   : Mon, 30 May 2022 23:59:59 GMT
Sunset                        : Sat, 25 Jun 2022 23:59:59 GMT
Date                          : Fri, 30 Dec 2022 11:34:54 GMT

Body:
{
  "error": {
    "code": "",
    "message": "No HTTP resource was found that matches the request URI 'https://igaelm-asev3-ecapi-cus.igaelm-asev3-environment-cus.p.azurewebsites.net/api/v1/accessPackageCatalogs('7f66090e-11d2-4868
-bc13-df98a327077d')/customAccessPackageWorkflowExtensions('65e8bcfd-c486-4c7b-9832-5ea25d398ac7')'.",
    "innerError": {
      "date": "2022-12-30T11:34:55",
      "request-id": "7605d105-7ebc-4378-9374-02526c9489ac",
      "client-request-id": "7605d105-7ebc-4378-9374-02526c9489ac"
    }
  }
}


Update-MgEntitlementManagementAccessPackageCatalogCustomAccessPackageWorkflowExtension : No HTTP resource was found that matches the request URI 'https://igaelm-asev3-ecapi-cus.igaelm-asev3-environmen
t-cus.p.azurewebsites.net/api/v1/accessPackageCatalogs('7f66090e-11d2-4868-bc13-df98a327077d')/customAccessPackageWorkflowExtensions('65e8bcfd-c486-4c7b-9832-5ea25d398ac7')'.
At line:2 char:1
+ Update-MgEntitlementManagementAccessPackageCatalogCustomAccessPackage ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: ({ AccessPackage...flowExtension }:<>f__AnonymousType312`3) [Update-MgEntitl...xtension_Update], RestException`1
    + FullyQualifiedErrorId : Microsoft.Graph.PowerShell.Cmdlets.UpdateMgEntitlementManagementAccessPackageCatalogCustomAccessPackageWorkflowExtension_Update
DEBUG: [CmdletEndProcessing]: - Update-MgEntitlementManagementAccessPackageCatalogCustomAccessPackageWorkflowExtension end processing.

And below the existing custom extension:

PS C:\temp\m365DSC\Backup\AADEntitlementManagementAccessPackageCatalog> 
Get-MgEntitlementManagementAccessPackageCatalogCustomAccessPackageWorkflowExtension `
    -AccessPackageCatalogId '7f66090e-11d2-4868-bc13-df98a327077d' `
    -CustomAccessPackageWorkflowExtensionId '65e8bcfd-c486-4c7b-9832-5ea25d398ac7'

Description DisplayName Id                                   CreatedDateTime     LastModifiedDateTime
----------- ----------- --                                   ---------------     --------------------
custext     custext2    65e8bcfd-c486-4c7b-9832-5ea25d398ac7 20/12/2022 17:50:08 20/12/2022 17:50:08 

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 with the Update-MgEntitlementManagementAccessPackageCatalogCustomAccessPackageWorkflowExtension entry point and compare its generated request with the linked Microsoft Graph beta documentation, focusing on the PATCH versus PUT discrepancy. Trace the metadata that produces this cmdlet and use the supplied debug reproduction to verify the resulting HTTP method and response.

Written by the indexing model from the issue text.

Assessment

Tech stack
powershell
Domain
api, tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.