Update apis (#14823)

* update api to v1

* change APIs to v1

---------

Co-authored-by: Pratham Rathi <prathamrathi@microsoft.com>

Author: PrathamRathi

application-workloads/identity-governance/byod-logic-app/README.md

@@ -201,23 +201,22 @@ After deploying the Logic App and assigning the required API permissions, you ne
 
 3. **Link the Logic App** — When configuring the CDPR, select the **Resource Group** where you deployed the Logic App, then pick the Logic App by name from the dropdown. This binds the Logic App's HTTP trigger endpoint as the callback URL for the BYOD flow.
 
-4. **Create an Access Package** — Still within the same catalog, create (or update) an **Access Package** and add the CDPR as a resource. Configure an **Access Review** policy on the package. When the Access Review runs, Entitlement Management will automatically call the Logic App with the appropriate trigger payload (`catalogId`, `resourceId`, and `data`) to start the BYOD data upload.
-
 ### Steps (Microsoft Graph API)
 
-You can also attach the Logic App to a CDPR programmatically using the Microsoft Graph beta API. All requests below use the endpoint `https://graph.microsoft.com/beta` and require a bearer token with the `EntitlementManagement.ReadWrite.All` permission.
+You can also attach the Logic App to a CDPR programmatically using the Microsoft Graph API. All requests below use the endpoint `https://graph.microsoft.com/v1.0` and require a bearer token with the `EntitlementManagement.ReadWrite.All` permission.
 
 #### 1. Create a catalog (skip if you already have one)
 
 ```http
-POST https://graph.microsoft.com/beta/identityGovernance/entitlementManagement/accessPackageCatalogs
+POST https://graph.microsoft.com/v1.0/identityGovernance/entitlementManagement/catalogs
 Content-Type: application/json
 Authorization: Bearer <token>
 
 {
   "displayName": "My BYOD Catalog",
   "description": "Catalog for BYOD resources",
-  "isExternallyVisible": false
+  "state": "published",
+  "isExternallyVisible": true
 }
 ```
 
@@ -228,13 +227,13 @@ Save the `id` from the response — this is your `catalogId`.
 This creates the Custom Data Provided Resource and configures the Logic App as the notification endpoint in a single request:
 
 ```http
-POST https://graph.microsoft.com/beta/identityGovernance/entitlementManagement/accessPackageResourceRequests
+POST https://graph.microsoft.com/v1.0/identityGovernance/entitlementManagement/resourceRequests
 Content-Type: application/json
 Authorization: Bearer <token>
 
 {
-  "catalogId": "<catalogId>",
-  "accessPackageResource": {
+  "requestType": "adminAdd",
+  "resource": {
     "@odata.type": "#microsoft.graph.customDataProvidedResource",
     "displayName": "BYOD Data Provider",
     "description": "Uploads external data via Logic App for Access Reviews",
@@ -248,7 +247,9 @@ Authorization: Bearer <token>
       "url": "<logic-app-trigger-url>"
     }
   },
-  "requestType": "AdminAdd"
+  "catalog": {
+    "id": "<catalogId>"
+  }
 }
 ```
 
@@ -266,13 +267,13 @@ Authorization: Bearer <token>
 If you already created a CDPR without a notification endpoint, you can update it:
 
 ```http
-POST https://graph.microsoft.com/beta/identityGovernance/entitlementManagement/accessPackageResourceRequests
+POST https://graph.microsoft.com/v1.0/identityGovernance/entitlementManagement/resourceRequests
 Content-Type: application/json
 Authorization: Bearer <token>
 
 {
-  "catalogId": "<catalogId>",
-  "accessPackageResource": {
+  "requestType": "adminUpdate",
+  "resource": {
     "@odata.type": "#microsoft.graph.customDataProvidedResource",
     "displayName": "<existing-cdpr-display-name>",
     "description": "<existing-cdpr-description>",
@@ -286,16 +287,18 @@ Authorization: Bearer <token>
       "url": "<logic-app-trigger-url>"
     }
   },
-  "requestType": "AdminUpdate"
+  "catalog": {
+    "id": "<catalogId>"
+  }
 }
 ```
 
-> **Note:** The `requestType` is `"AdminUpdate"` instead of `"AdminAdd"`. The `originId`, `displayName`, and `description` must match the existing CDPR.
+> **Note:** The `requestType` is `"adminUpdate"` instead of `"adminAdd"`. The `originId`, `displayName`, and `description` must match the existing CDPR.
 
 #### 3. Verify the CDPR was created
 
 ```http
-GET https://graph.microsoft.com/beta/identityGovernance/entitlementManagement/accessPackageCatalogs/<catalogId>/accessPackageResources?$filter=originSystem eq 'CustomDataProvidedResource'
+GET https://graph.microsoft.com/v1.0/identityGovernance/entitlementManagement/catalogs/<catalogId>/resources?$filter=originSystem eq 'CustomDataProvidedResource'
 Authorization: Bearer <token>
 ```
 

application-workloads/identity-governance/byod-logic-app/azuredeploy.json

@@ -302,7 +302,7 @@
                           },
                           "type": "Http",
                           "inputs": {
-                            "uri": "@{parameters('graphEndpoint')}/beta/identityGovernance/catalogs/@{triggerBody()?['catalogId']}/accessPackageResources/@{triggerBody()?['resourceId']}/uploadSessions",
+                            "uri": "@{parameters('graphEndpoint')}/v1.0/identityGovernance/catalogs/@{triggerBody()?['catalogId']}/resources/@{triggerBody()?['resourceId']}/uploadSessions",
                             "method": "POST",
                             "headers": {
                               "Accept": "application/json",
@@ -434,7 +434,7 @@
                               },
                               "type": "Http",
                               "inputs": {
-                                "uri": "@{parameters('graphEndpoint')}/beta/identityGovernance/catalogs/@{triggerBody()?['catalogId']}/accessPackageResources/@{triggerBody()?['resourceId']}/uploadSessions/@{outputs('Compose_Session_Id')}/uploadFile",
+                                "uri": "@{parameters('graphEndpoint')}/v1.0/identityGovernance/catalogs/@{triggerBody()?['catalogId']}/resources/@{triggerBody()?['resourceId']}/uploadSessions/@{outputs('Compose_Session_Id')}/uploadFile",
                                 "method": "POST",
                                 "headers": {
                                   "Content-Type": "multipart/form-data; boundary=testboundary"
@@ -486,7 +486,7 @@
                           },
                           "type": "Http",
                           "inputs": {
-                            "uri": "@{parameters('graphEndpoint')}/beta/identityGovernance/catalogs/@{triggerBody()?['catalogId']}/accessPackageResources/@{triggerBody()?['resourceId']}/uploadSessions/@{outputs('Compose_Session_Id')}",
+                            "uri": "@{parameters('graphEndpoint')}/v1.0/identityGovernance/catalogs/@{triggerBody()?['catalogId']}/resources/@{triggerBody()?['resourceId']}/uploadSessions/@{outputs('Compose_Session_Id')}",
                             "method": "PATCH",
                             "headers": {
                               "Accept": "application/json"
@@ -513,7 +513,7 @@
                           },
                           "type": "Http",
                           "inputs": {
-                            "uri": "@{parameters('graphEndpoint')}/beta/identityGovernance/catalogs/@{triggerBody()?['catalogId']}/accessPackageResources/@{triggerBody()?['resourceId']}/uploadSessions/@{outputs('Compose_Session_Id')}",
+                            "uri": "@{parameters('graphEndpoint')}/v1.0/identityGovernance/catalogs/@{triggerBody()?['catalogId']}/resources/@{triggerBody()?['resourceId']}/uploadSessions/@{outputs('Compose_Session_Id')}",
                             "method": "PATCH",
                             "headers": {
                               "Accept": "application/json"

application-workloads/identity-governance/byod-logic-app/metadata.json

@@ -5,15 +5,15 @@
   "description": "This template deploys a request-triggered Logic App for Microsoft Entra Entitlement Management with AADPOP authentication policies for secure webhook-based integration.",
   "summary": "Deploy a request-triggered Logic App for Microsoft Entra Entitlement Management BYOD scenarios.",
   "githubUsername": "prathamrathi",
-  "dateUpdated": "2026-06-02",
+  "dateUpdated": "2026-07-23",
   "environments": [
     "AzureCloud"
   ],
    "testResult": {
     "deployments": {
       "templateFileName": "azuredeploy.json",
-      "correlationId": "c1aa69a5-4c58-488b-be2f-009e87a11853",
-      "deploymentName": "Microsoft.Template-20260602155251"
+      "correlationId": "45fb9d94-d822-40f9-a08c-389b260d147c",
+      "deploymentName": "CustomDeployment-20260723113556"
     }
   }
 }