Views:

Applies to Product - Dynamics 365 Business Central


What’s happening?
Users are unable to access Business Central despite having the necessary licenses and permissions. This issue may occur after changes to user licenses or when accessing the application through a Granular Delegated Admin Privileges (GDAP) relationship.


Reason:

  • Users may lose access to Business Central if their licenses are modified or removed incorrectly.
  • There may be a known issue affecting specific environments, particularly in certain regions, which prevents users from logging in.
  • The system may not recognize the delegated admin user due to configuration issues or bugs in the application.
Resolution:
License Management:
  1. Verify that the users have the correct licenses assigned in the Microsoft 365 tenant. Ensure that the necessary licenses are active and properly configured.
  2. If users have lost access after license changes, unassign and then reassign the appropriate licenses to the affected users.
GDAP Configuration:
  1. Confirm that the GDAP relationship is correctly established and that the partner has the necessary permissions to access Business Central.
  2. Check that the partner's user account is set up as a valid user in Dynamics 365 Business Central.
Additional Troubleshooting Steps:
  1. If users are still unable to access Business Central, check for any known issues reported in the relevant support channels or forums.
  2. Review the error messages received during login attempts and gather detailed logs to assist in troubleshooting.
  3. If the issue persists, escalate the case to the appropriate technical team for further investigation.
Potential Workaround:
  1. As a temporary solution, consider using the "External Accountants" access if applicable, while the main issue is being resolved. Note that this may require additional licenses.
Follow-Up:
  1. After implementing the above steps, follow up with the affected users to confirm if the issue has been resolved. If not, continue to monitor the situation.
If the issue remains unresolved after these steps, further investigation may be required to identify underlying system bugs or configuration errors.