You’re offline. This is a read only version of the page.
Announcements
5
Hello,
I'm a newbie and have recently set up a new environment for Dynamics 365 app. I followed the instructions for creating the environment and the correct licenses. When trying to add the Dynamics 365 app to Teams I get the following error for the new environment. Can someone point the way to my next step in troubleshooting this?
Thank you.
Shaun
Thanks, Lorne - I will do. I really appreciate your help - very generous of you to share your knowledge and expertise with a random. Have just connected with you via LinkedIn mate. Cheers from the Sunshine Coast, Australia
Well, I'm biased as I'm an MS partner. That said, if this is for production use and you want the power and capabilities of D365 along with the rest of the O365 platform (Teams, SharePoint, ODfB, etc.) and don't want to invest more time interacting with the vendor (with the possibility that their product may no longer be able to enable the Teams integration), then getting a normal, paid D365 subscription would be the way to go. But, as I said, I want to be transparent that I'm a partner and I'm pretty stoked at the massive progress MS has made with the Dynamics cloud over the course of the last 4 release "waves". Across all the service lines. So, I guess take it with a grain of salt?
I've already adjusted my admin settings by doing as you suggested. Pretty much, I control the world now. Many boxes are checked :-)
After coming this far, I wonder if it is just more prudent to shell out for a proper D365 license now rather than try and self-support (and with the support of good folks like you) and come up against some technical glitch in the future which will just waste time and affect my data. All my client information will sit inside here. I'm thinking proper D365 - you?
Well, that's....interesting. Before I give up and suggest contacting a vendor you've said is "Not very good at answering questions though", try creating a 2nd global admin in your O365 admin center, edit your usual global admin account to add the roles, and then try the new instance you created.
What you're saying makes sense Lorne. I'm just confused as a forum screenshots below shows that the same installation was working in Teams. There were a couple of other people with the same issue as me a while back and this was the response - this guy is the head of RapidStartCRM. Not very good at answering questions though :-( I guess they want you to subscribe to the paid service.
You've been a great help to me Lorne and I'm thankful for your time. Could there be an other direction I can take this or is it dead in the water in your opinion>
Regards,
Shaun
My bad, Shaun. I didn't eplain as clearly as I probably should have. At the very top of the page for the link for this RapidStartCRM product they say "RapidStartCRM is a Power App that requires a Power Apps CDS Environment to be in-place to install it on". And it is that part highlighted that is the issue. They're not providing you a D365 instance. They're providing their own solution that is PowerApps based and may well contain copies of some of the entities and relationships and such from D365, but that is not the same as a full D365 instance and the Power Platform Admin center knows that you don't have all the pre-req's for the Teams integration (even basic). Hence, the option isn't even visible in the system settings.
Thanks Lorne - that workaround makes sense and I'll try it :-)
I was using it under the Default environment as I came to understand that this wouldn't work. I went through and started a new environment to add a fresh install to. But, still the same issue. So, in your opinion - does this issue circle back to your first point about permissions again?
The inability to edit your own role as an admin on O365 admin center is expected behaviour. Even as global admin. Makes no sense to me but you get around that by assigning global admin to another user, logging in as that user, and editing your user.
However, the key comment from your reply was "I've been using it under the default environment". The default environment is a common data service environment so the integration to Teams isn't available for that. It has to be a new environment and has to be of the D365 CE type, not CDS.
Hi Lorne,
Thanks for all your help so far.
Yes, I'm Global Admin. It's just me in my org besides a few Users who are part of my Teams set up.
The manage admin roles set up is greyed out though and the error says I can't change my own settings. Hmmm.
In the admin roles it gives me the option to be D365 admin but is unchecked.
I am not sure where to find the zTeams admin permissions for my tenant. But the manage admin roles gives me the options for Teams admin - but also unchecked and I cannot change that.
I'm not sure of the technicalities of 'full D365 instance' vs 'Common Data Service' - sorry. I've copied in the link to the install instructions I followed as it has screenshots hoping this will give the answer to your question. The D365 version is pre-packaged no-cost version from RapidStartCRM. I've been using it under the default environment but not as an integration with Teams so am starting again with a fresh install. Go to;
https://rapidstarthub.com/the-original-rapidstartcrm-installation/
Okayyyyy. Then let's check some other things:
#1
André Arnaud de Cal...
291,359
Super User 2024 Season 2
#2
Martin Dráb
230,370
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (
