Applies to Product - Dynamics 365 Lifecycle Services
What’s happening?
Customers have requested to rotate the passwords for their batch jobs and are uncertain if this is acceptable or if downtime is required, as well as how it might impact the operations of their systems.
Reason:
Batch jobs are run under the context of a user account, but the passwords are managed in Azure Active Directory (Azure AD) and not within the application itself.
Resolution:
- There should not be any downtime needed since the passwords are managed outside of the application.
- Customers can make the password changes during off hours or coordinate with business users to determine the best time for the changes.
- It is recommended to test the process in a sandbox environment by changing a batch to a different account that is not used in production, confirming that the batch jobs run as expected, and then changing the account password to ensure the batch job continues to run after the password change.
- If any issues arise during the password change in production, it may be necessary to create a new high-severity support case if it is critical.