Identity
3 TopicsUpdate App Registration Client Secret Using Microsoft Graph REST API v1.0
Hello, I have a customer who wants to set the App registration Client Secret to 1 year. Here are the customer's requirements: For existing application registrations under ‘Certificates & Secrets’ pane, any new secrets added by owners should have the duration limited to one year. If the owner tries to set the duration greater than one year and clicks ‘Add’ button, the action should not be allowed with proper error displayed. The same behavior should also be applicable to new application registration specific secrets. It should not impact any existing secret that is present (greater or less than one year) for current application registrations. We need a way to enable and disable the global policy in case we want to disable it if something doesn’t work as expected. We don’t want to impact anything else wrt application registrations or anything in service principles. Based on the article you shared; Microsoft Entra application management policy API overview - Microsoft Graph v1.0 | Microsoft Learn Below is the script we are trying to use to add the global policy and set as default policy with isEnabled = true. As we cannot test in a different tenant, can you please confirm the snippet below will work for the above requirements? MgPolicyAppManagementPolicy | select * $policy = @{ "displayName" = "Enforce Max Lifetime for Secrets" "description" = "Policy to enforce a maximum lifetime of 1 year for any new secrets." "applicationRestrictions" = @{ "passwordCredentials" = @{ "maxLifetime" = "P365D" # ISO 8601 duration format for 1 year } } } New-MgPolicyAppManagementPolicy -BodyParameter $policy Update-MgPolicyDefaultAppManagementPolicy -id <ABOVE_POLICY_ID -IsEnabled $true I tried to test it in my own tenant, but I ran to a permission issue. Can someone please confirm if this snippet works against the customer's requirements? Thanks.616Views0likes4CommentsSet up question for Azure Privileged Identity Management
Tell me if my setup is correct. I need to create an access package for some users for User Management so they can request the package through MyAccess.Microsoft.com . This is what I did. - AAD I created M365 Group and named it "UserAdmin-Corp" and added this group to the AAD Role User Administration Active Assignments -In Identity Governance --> I created a Catalog and added the UserAdmin-Corp to it as a resources - Created an Access Package Add the UserAdmin-Corp and manage the remaining settings such as Lifecycle duration. Is this setup correct to create an access package. Based on my try, the user login to MyAccess and see the Package, request the access and the user automatically added to the group, and once the duration is over, the user automatically removed. I am not sure if the way i setup it is correct, even though it seems to be working. actually I am not sure that should the group be in the Active Assignment or the Eligible Assignment. ThanksSolved1.4KViews0likes3Comments