Do you want to give view (read only) access to all colleagues for your ERP system without needing to buy additional licenses?
When an organisation has both a Dynamics 365 Business Central and Microsoft 365 subscription, administrators can configure environments to enable access with Microsoft 365 licences, and choose exactly which tables and other objects this category of user will have access to.
When configured, employees that have a Microsoft 365 licence but no Business Central licence can view Business Central records that are shared with them in Microsoft Teams chat and channels.
You can read the full Learn article here Business Central Access with Microsoft 365 licences - Business Central | Microsoft Learn
In this post I'll run through the config needed to setup this M365 access to D365BC.
Firstly you might be wondering what is considered an M365 license for the purposes of this Teams access to D365BC, here is the list:
![](https://blogger.googleusercontent.com/img/a/AVvXsEi4hGPKd-UZhwE9EU8tJdAMPUp_bQro_x47Vh6KQoQPM_7z9fb7nGqmwh0IlPwdqhAJEOPgCJvOq7FEFaBWkaXSgynmiycD_w9GHo2AEYwIIn0y_Q5w-NsL-uhP95ApXp-GmKTbSnGTfw_JZLxjRRfWTvHBqovreDpGAGWi21zzyMs0CsmEiqNQ) |
Any of these Microsoft 365 will work for the BC access in Teams |
The feature is managed on the BC admin portal where there is an on/off control:
![](https://blogger.googleusercontent.com/img/a/AVvXsEhMmvYQvUqGnVVaFo3DuNV4YxGcHBespNSmrPaLn8ObK-KEKZpuLQPIOJnR-I0qGIAI3APxVQBMTgwa353ZLbJwoa094aWk0wCGciDlXDrn58IS7TKZ0S_8NDbPRdIgmFMZD5RkYBMv-PYrKlMIfKXefFxWfyzs8NlrG5Swq6HjoihrPA3vZJN2) |
D365BC Admin portal, showing the M365 access feature control |
Best to prepare a few things before you turn it on. I will create an Entra Group (aka Azure Security Group) that will manage the permissions granted to the M365 users. In this simple example I want to simply grant read access to anything mu BC users share to teams and I created a group named "BC Read All"
![](https://blogger.googleusercontent.com/img/a/AVvXsEjAq1_rmbTJrpSY7ZSdJ5AuftOweQ-LwyMFAf1yU-koJ4vivkJ_6Ea6etP0KJ3A1aJYO4oBBoJIJgjXou1MLUR77wrUHBr-ZssthPyvvyC3AqmyO7LffJXVVAXKJZm2iUUMOuljMxPeA6mjEb_4L-RsRUvAXZlSWDtrSTTp5YP6alIcOY3-zO8G) |
Microsoft Entra admin center showing the "BC Read All" group |
Next I'll set the permissions for this security group in BC and clear out the License Configuration for M365 Licensed users - to ensure all control is managed by the Security Group (see here for more on that approach Simplify your user onboarding process with Dynamics 365 Business Central & Azure Security Groups)
![](https://blogger.googleusercontent.com/img/a/AVvXsEgexit8fFe2zbJbEnGDFqp9PMW1c991eTfFAUww1UnOnwrt9jqdAtHL3SsEQt4SVIVr3_UreruXLw9Jz5G0vSSiw2qve9A06dA29GJA5WzeZNyn67yqtZTZk3814Ibu9g4anuT67eS11s1xSBFPdQxT18AdtyGwkdPhrIBkQJajwrEFwPuwiJOn) |
Permissions config on the Security Groups page for "BC Read All" |
![](https://blogger.googleusercontent.com/img/a/AVvXsEjC9omP3eb4-tygRd2Nk-LI-Cgf7gcpz6amJ5bMxLtSr0N-JyccVuPOiV_-hFAWkb6E_4D40Njx9vTLJg8D4fuwQXo1rII1VjZ9_QZleoyKPbikoFuno7ZJfki-hR4_XWQfS3zCqHxylcQJsM9CWvYZlfCH74pgFm9vh48FrM8B8nUrjAf_2WLS) |
Cleared out License config for Microsoft 365, this ensures all permissions are managed by the above Security group config. |
Lets turn on the feature now access the Dynamics BC admin page and run though the steps
![](https://blogger.googleusercontent.com/img/a/AVvXsEgSIMUK3yUAKiIaIgbdFg4RWFH4fY7LgKDnhTA-YWVWE8a-Ag8CbFwxb1lA1X51WuuUriRfHkmYI-Ev5TiZLZj_pRgk5gawEbVVIyRcQ_Kauzrl6qLbq2_jFheM7vonkqtQ3qCCqbucrejTwJsYZ-8L7IsjUSksd4F48fjzBIsBR1jAZkPdj2AK) |
Turn on the features in the admin portal |
![](https://blogger.googleusercontent.com/img/a/AVvXsEi9csITeqH_ZKibO_v_YKGHivLELMN_cTyJWqb2T5SNkR5NQu_ll3l3D1KIrS3vccNcBzy4AgHcOOm7dpvVC3_g-BWJOMKmu5StfkQewHZAxA5Z04FrHK25AicMUbSpU6LRfY-tN6lN0hyq9G74W6PVvu-onBpniSH05EUMCxurFRUlTuQFsSvq) |
We already prepared the permissions so its fine to choose "Don't restrict access" |
That's it - lets test it out now. For an M365 user to view BC records they need to be shared to Teams; here I have shared the Purchase Order list and pinned it as a tab
![](https://blogger.googleusercontent.com/img/a/AVvXsEiuWA67wl-yaN_1oNtJMO4YjH3VrpOoFsh1rXrt7DRO_V7Try-Sw9DJv35VV29LPO57WWeEjUU91P2DevNFCTQkgh8kATeP1m1tolv1nHoLTZBOpnx_CXrNN_hxk4FYu6MiitYVSJK1VRWWrG0z4jUMmO4CnptzMi1E3MK6Mf2Us3dLnh8i2mr2) |
A BC user sharing a list page to teams
|
![](https://blogger.googleusercontent.com/img/a/AVvXsEiLspoYUqtQcr3THcH45GE_Noeyjxj96XFcEftx3ABCy-dTD2dtjYLkuG6xfO6XqBdLoWLEUgKSjk15465wuqDpGKTS0oTrYC5Sg-Z63y24kqJxafdfAM5ipIjcj5YDM2tsdUhQkP-PC0Q3BMgDhTg2KypWxfYzzJdDbVTZq9bjR34RanM886AB) |
Pick the team channel to share to |
Now, I've logged into Teams web as Grady, my example user who has an M365 license and no BC License
![](https://blogger.googleusercontent.com/img/a/AVvXsEgyaWG1W_7RGua0MPZxKwxEvIJF50SMKpt8aI5xR_8WwUj27rkm8KEHa6s456EVKp_itL4RjRPBcY_R4RZVLZAF7kXqD-5coSbpZJLi2dvNw1R85HdNJTGGq6aevhYdFqHD9mbgLDrEIiPFMr3Y0x0UhYP3-YHSeRdFImUsj5AoSsPmJ3IzUzf4) |
Just to check what licenses Grady has |
Here is the Teams channel the BC user shared the PO list to
![](https://blogger.googleusercontent.com/img/a/AVvXsEira_ixDzZ6n_18YwAS6pbpWkKCJ_nvq1Q9gmE0d2B2NgZhehMWfgqVY5cwj9Q7Xu9cCn7IhdB6nzlahZ281_x_VnK6u42hNdXJ9iAxRgka2YXE-Oi4c3WwazQVxpvo-nByqQ-IyrPy7w0R2lAVhfDNFsDX_PXw03icQjsgcdCVIJaV-FJcfO4X) |
Teams channel with content shared from BC by BC users |
Grady can view the list by clicking on the "Details" action and optionally pin as a tab for handy future access to all POs
![](https://blogger.googleusercontent.com/img/a/AVvXsEhqqJAVEwYqN_vomDvhOmb09YhAaJ_L47QHG0_CRJ7FNBYBkP2HkV9Rn5CnenXGrM4J4wnaXkNG86E8SrbXPDnhlmvXWboOB8tEKpoTTEgAigUVhqA50buHg0FHftBDyfwIlLoQKhrNSs-coVz-WgIO3mUoqRnFPB6lg1ghxO50q8lvV0isvdfq) |
The PO list page opened in Teams by Grady, our M365 user |
![](https://blogger.googleusercontent.com/img/a/AVvXsEgANboko9SjitY1Ph5bztB1NzuSMVuXizkZWchss-uB0TqoMIu6yKPjSC2jUzdo2uX3sVrQjhAENr5_ewWvLnRdDAnvHM4y4cCR334B2KGcdvlWDx1QdJkbqV-f2ekThV-S9pMnarNboqt1cN_yH7Q5D4e4JoKqHqJYtyF5SUlwumu_sOUDagyk) |
Grady is now using the tab and tab chat to collaborate on these records |
![](https://blogger.googleusercontent.com/img/a/AVvXsEicgalSRcaRm_7ViWSunfIampEtTREtjyVgAgrrpx1xk_PVa44BgGXj4XqRx40C_BExJyvg3cy_gzWz5Pd9mpLm8dnfvtSjOKfAZE-DMU1AgePbWfbzbpufPcf0sC51seHdae5A_YRWnwR3CopRd1BL9EuuVKeeWOz3l3NxMiM6i_KoU1rj0L6i) |
Individual documents can be viewed from the list |
There we go 'free' access to BC for your M365 users!
The final bit of setup you may want to consider is the layout of the document presented in Teams, unlike a BC user accessing a page in the BC web client, M365 users accessing BC in Teams have no control of the layout.
To manage this a BC admin should be mindful of the default profile in BC as that will be assigned to the M365 users when they access a BC object for the first time:
![](https://blogger.googleusercontent.com/img/a/AVvXsEhfgUYcjwKX5fFpaF5zZ0mI5gdTExa6MUMW_12B16u3r9zyIPdy70yA7887y7L8Xu1fwhilI4ltYpbWeSY6M8ZF3HfRqBR1zWTrr5U_Y7o63RTxc8ecPeq4Lrzj6SiCTBrHMQhRP7HA-BY4FotoA1Wixi3bOE4JRVz2LihjRw_DjlVLEEm43dtT) |
caption |
Then use the Customise Pages to set any layout for this profile, in this example the Vendor Order number was a handy which I've added:
![](https://blogger.googleusercontent.com/img/a/AVvXsEiINErGctHKUyyd14hZ0lJ4xfcbamIkFMAwoI1BN2ipgkjbKFUIvxSh2r0HfiYMfV7NsFIk9JVoLSiybA_TsJ8xjoNgAM3rJI_M4WQcOl8OvXk2qaIyoj3PdT0AwI_vGiX1nEpiE3ZVTkf11vZmM-krj8S4hLjItE3Sy65xpyClL4Pw-gW7kLSc) |
Customise pages, navigate to the page, and drag/drop field you want
|
Back in Teams - since Grady has been assigned that Business Manager profile - that's the view he will get.
![](https://blogger.googleusercontent.com/img/a/AVvXsEj6Ts3PqtNCfJZA_piJoWUWsXxXQcPHz8PzZYsAIM2mksKXW3kZxh8WEXRXBqGWOpILurC9YHnsyo43M1kzAzkpjNHMdXu4trSkTCSDun59tswi8669sXdUPN_NU4KZoGryMjbR6SOmAszPDW4iK8FaYLlc3CJxFtCIuvty7tcq-rzA4u6fDnfD) |
Back in teams as Grady, to see the updated layout |
Summary
I have shown the steps to grand access to your M365 users, we ran through an example of an M365 user and we finally tailored the view that the M365 user got in Teams through the Profiles (Roles) > Customise pages features.