How to configure app instance property lock for your applications (Preview)
Application instance lock is a feature in Azure Active Directory (Azure AD) that allows sensitive properties of a multi-tenant application object to be locked for modification after the application is provisioned in another tenant. This feature provides application developers with the ability to lock certain properties if the application doesn't support scenarios that require configuring those properties.
What are sensitive properties?
The following property usage scenarios are considered as sensitive:
- Credentials (
keyCredentials
,passwordCredentials
) where usage type isSign
. This is a scenario where your application supports a SAML flow. - Credentials (
keyCredentials
,passwordCredentials
) where usage type isVerify
. In this scenario, your application supports an OIDC client credentials flow. TokenEncryptionKeyId
which specifies the keyId of a public key from the keyCredentials collection. When configured, Azure AD encrypts all the tokens it emits by using the key to which this property points. The application code that receives the encrypted token must use the matching private key to decrypt the token before it can be used for the signed-in user.
Configure an app instance lock
To configure an app instance lock using the Azure portal:
Sign in to the Azure portal.
If you have access to multiple tenants, use the Directories + subscriptions filter
in the top menu to switch to the tenant that contains the app registration you want to configure.
Search for and select Azure Active Directory.
Under Manage, select App registrations, and then select the application you want to configure.
Select Authentication, and then select Configure under the App instance property lock section.
In the App instance property lock pane, enter the settings for the lock. The table following the image describes each setting and their parameters.
Field Description Enable property lock Specifies if the property locks are enabled. All properties Locks all sensitive properties without needing to select each property scenario. Credentials used for verification Locks the ability to add or update credential properties ( keyCredentials
,passwordCredentials
) where usage type isverify
.Credentials used for signing tokens Locks the ability to add or update credential properties ( keyCredentials
,passwordCredentials
) where usage type issign
.Token Encryption KeyId Locks the ability to change the tokenEncryptionKeyId
property.Select Save to save your changes.
Feedback
Submit and view feedback for