Deployment was successful and App loaded in Teams. But no logon button under Welcome

[matt-mansol]

I think I've missed something or entered something incorrectly in the config.

The deployment completed successfully:

Enter site template XML schema file path: C:\Administrative\TEOC\Deployment\provisioning\EOC-SiteTemplate.xml Enter tenant name: (contoso): mansol Enter tenant admin email: teoc-admin@mansoldomain.com Enter site name. Allowed characters for site name are underscore, dashes, single quotes, and periods (,-,',.), and can't start or end with a period.: TeamsEOCSite_
_PnP.PowerShell module found Checking if site already exists at /sites/TeamsEOCSite Site doesn't exist, creating new site at /sites/TeamsEOCSite https://mansol.sharepoint.com/sites/TeamsEOCSite Creating lists in TeamsEOCSite site App Provision complete.__

I can open the App in Teams and it displays the header info and 'Welcome 'username'.' but nothing under that.

I initially had the problem where I overlooked adding the accessTokenAcceptedVersion and updating the value from null to 2 in the application manifest. But I haven't been able to see why this isn't working. I can see that there are "400 (Bad Request)" in the console logs which are attached. But I don't understand where to update that config to correct.

Please help :) TEOCConsoleLog.txt

[v-ajaysahu]

@matt-mansol , thank you for reporting this issue. We went through logs which you've shared. App is not able to access SharePoint site. Please check the API permission and Site Permission.

[matt-mansol]

I have checked and confirmed the API permissions appear to be set correctly.

And I can confirm that the "Everyone except external users" is invited as a Member [Edit] to the site.

[v-ajaysahu]

@matt-mansol , Can you clean-up azure resource and re-deploy the TEOC app. Since while configuring you've missed something. Kindly follow this link while deploying.

[matt-mansol]

Ok. I deleted the Apps and did it again. This time, I am now presented with a Login button in the Teams App, but when I click it I am presented with the error

_Sign in Sorry, but we’re having trouble signing you in.

AADSTS700016: Application with identifier '938d39e6-f039-40d0-bfe6-656e01d0281b' was not found in the directory 'Managed Solutions'. This can happen if the application has not been installed by the administrator of the tenant or consented to by any user in the tenant. You may have sent your authentication request to the wrong tenant._

That App ID in the error message matches the previous Azure AD application that I originally provisioned.
The application with that ID no longer exists..

[v-ajaysahu]

@matt-mansol , Did you remove TEOC app from MS Teams admin center and deployed the TEOC app with new client Id which you've created? If not then please remove the app and deploy it. You can follow from this link.

[matt-mansol]

Yes I did.

However, I can see that even after removing the app again from Teams Admin Center, that the old App is still listed in MS Teams webclient. If I try and uninstall from the webclient it has an error message.

There was an issue while trying to remove TEOC. Please try again

Presuming this is due to the app no longer being available. I've also added the app back in, and tried to uninstall from the webclient. It results in the same error.

[matt-mansol]

I have managed to fix the app. Turns out it was a cached 'personal app'. I had to clear my local client v2 cache. And then I simply had to upload the new version and wait for it to be available to me.

However, I'm back to where I began with the blank TEOC app. I can open the App in Teams and it displays the header info and 'Welcome 'username'.' but nothing under that.

In reviewing the console log - I'm getting different errors this time.

240419-TEOCConsoleLog.txt

Update: I have also now fully recreated the SharePoint site in case it didn't provision successfully. The site provisioned perfectly.

But the same problem remains.

[matt-mansol]

I can appreciate that this isn't a paid service. But honestly, the lack of help is a bit disappointing.

TEOC is a great idea and I'd love to be able to demonstrate this to my team but if I can't get it working, it might be more feasible to go with a better developed product where there is vendor support.

[v-ajaysahu]

@matt-mansol , I apologize for the inconvenience caused. Can we connect to resolve this issue? Please share your email address and your availability for MS Teams Call so that we can connect with you to fix it.

[matt-mansol]

Hi v-ajaysahu,

This is the best email address to connect with me.

I’d really appreciate the help.

[v-ajaysahu]

@matt-mansol , Can you share email address and your available time from GitHub. If you respond via email then the email address will be hidden, and we won't be able to contact you. If you want, you can delete it once we connect with you.

[matt-mansol]

Apologies v-ajaysahu, I didn’t realise.

My email address is @.**@.>

And I’m next available 07/05/24 from 08:30am AEST (+10) onwards. I’m happy to try and be available at different times if necessary.

Thanks again for your help with this.

[v-ajaysahu]

@matt-mansol , Sharing my email address. Please email me so that we can connect since we are still not able to view your email address. << Removed >>

[v-ajaysahu]

@matt-mansol , I have scheduled a meeting for the 8th of May 2024 at 3:30 PM AEST. I hope this schedule works for you.

[matt-mansol]

That works fine!

Thank you so much. I look forwarding to speaking with you.

Matthew Jenkins Senior Systems Engineer P 1300 626 765 e @. w www.mansol.net.au d https://www.mansol.net.au/disclaimer IT Systems - Microsoft Specialists Comms | Data | Security | Electrical | Coolers Internet and Networking Qld Electrical Contractor Licence No: 75447 With over fifty people committed to providing the best IT and Internet support possible. Great people, great service, reliable computing. From: v-ajaysahu @.> Sent: Tuesday, May 7, 2024 8:07 PM To: OfficeDev/microsoft-teams-emergency-operations-center @.> Cc: Matthew Jenkins @.>; Mention @.***> Subject: Re: [OfficeDev/microsoft-teams-emergency-operations-center] Deployment was successful and App loaded in Teams. But no logon button under Welcome (Issue #190)

@matt-mansolhttps://github.com/matt-mansol , I have scheduled a meeting for the 8th of May 2024 at 3:30 PM AEST. I hope this schedule works for you.

— Reply to this email directly, view it on GitHubhttps://github.com/OfficeDev/microsoft-teams-emergency-operations-center/issues/190#issuecomment-2097932927, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BHSMF6ASG5T32W6QD6AI5GDZBCRVTAVCNFSM6AAAAABFYRGVSKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJXHEZTEOJSG4. You are receiving this because you were mentioned.Message ID: @.**@.>>

[v-ajaysahu]

@matt-mansol , Thank you for attending the meeting. Based on our discussion, please redeploy the application with the correct resource base name. After deployment, confirm if the application is functioning properly.

[matt-mansol]

Thank you again for your assistance Ajay!

As we found yesterday afternoon:

Re-deploying the resource with a correct base name (lower case) fixed the problem.

Uninstalling and re-adding the app in Teams then removed the cache and enabled us to see the working Ops Centre successfully.