Kenneth Kryger Gram Abakion CEO

It is amazing that we can create multiple Business Central production instances with a specific country release, but we also need the ability to select the Azure data center or region where a new production instance should run, so we can support where the primary users are located. Users working in a country production instance, may not be working in the same country, so to provide the best user experience, we need the production instance close to the users location

In Business Central on-prem we can manage user permissions based on Azure AD security groups, but in the SaaS version this is not an option. If a tenant has many users it is a very time consuming task to add permissions to each user. The current process is to add a BC license to users then update users from O365 in BC and then add/modify user groups. The preferred process would be to create new users in Azure AD/O365 portal and add relevant security groups and licenses. As today a users with a valid BC license logging into https://businesscentral.dynamics.com/ will be created automatically in BC and based on a mapping between AD security groups and BC user groups they should get the relevant user groups assigned including company limitations

When major updates are deployed by Microsoft all 3. party apps deployed form AppSource is updated as part of the BC major update, but when minor updates are deployed, 3. party apps are not updated. This can block an minor update because some apps need to be updated before the minor update can complete. If minor updates fail because of needed 3. party app updates, we need to update these apps manually. very time consuming Please add an option per environment to to push 3. party app updates as part of minor updates, so it works the same way as major updates.