Azure Managed Endpoints in Azure Machine Learning automatically manage keys for security. As you've noticed, these keys can change when you redeploy your models, which can cause complications when you need to share these keys with others, such as backend developers. Azure does not provide a way to set or maintain static keys for Azure Machine Learning endpoints. The system is designed to automatically generate new keys when you deploy a new version of your model for security reasons.
Maybe you can do the following as a workaround
Use Azure Active Directory (AD) to create a service principal, which is an identity that you can use for automated tasks and app integrations. You can grant this service principal the necessary permissions to access the Azure Machine Learning endpoint. The backend developer can then use the service principal's credentials to authenticate with Azure AD and access the endpoint, eliminating the need for keys.
or
Azure Key Vault is a service that lets you securely store and manage keys, secrets, and certificates. You could potentially use this service to store the keys for your Azure Machine Learning endpoint. Then, whenever you redeploy your model and a new key is generated, you can update the key in Azure Key Vault. Your backend developer could then access the key from Azure Key Vault instead of needing to receive it from you directly each time.