search

OfficeDev / microsoft-teams-emergency-operations-center

The Microsoft Teams Emergency Operations Center (TEOC) solution template leverages the power of the Microsoft 365 platform to centralize incident response, information sharing and field communications using powerful services like Microsoft Lists, SharePoint and more.
MIT License
90 stars 36 forks source link

New Deployment of TEOC 3.1. Pane is blank upon upload (step 8) #210

Closed GitRomney closed 3 months ago

GitRomney commented 3 months ago

When I upload the app into Teams, the pane is blank in Teams Desktop and Web indicates trouble reaching the url. I've reviewed closed support cases on this page to assist in troubleshooting but can't determine where the issue is after viewing the HAR logs myself.

Once you acknowledge the receipt of this case, I'll upload the HAR logs and manifest file I've collected, then delete them once you have them.

Thank you in advance for your help.

2024-06-24_08h59_431 2024-06-24_09h05_111

v-ajaysahu commented 3 months ago

@GitRomney , thank you for bringing this issue to our attention. Based on the provided screenshot, it appears that the URL added in the Manifest file may be incorrect. Please verify this. If you believe the URL is correct, then please share the console logs and network trace to help us troubleshoot the issue. Also, provide the manifest file that you have zipped and uploaded to the Teams Admin.

GitRomney commented 3 months ago

I have checked the URL and it matches the one in Azure. Please find the files you requested, attached. Please let me know once you have them so that I may remove them from here. Thank you for your help.

v-ajaysahu commented 3 months ago

@GitRomney , Yes, I have received the shared files. You can delete them.

GitRomney commented 3 months ago

Thank you. Please let me know if you need anything further from me.

v-ajaysahu commented 3 months ago

@GitRomney , I have reviewed the provided Manifest and logs. The URL included in the manifest is currently not accessible. Could you please verify the URL, or go to the app service, click on 'Browse', and check if the site is operational?

image

GitRomney commented 3 months ago

That URL was not in App Services but another URL was (the name of the App Service plan). We added the Service Principal as the redirect URI in step 4. The instructions were a bit confusing. After changing that and updating the manifest, we can now get to the login page, but get the message pictured. The client secret is valid (not expired). We're going back through the instructions again to see if maybe we missed something.

image

GitRomney commented 3 months ago

I'm not sure what we're missing. We're still getting the "No reply address provided" error, shown in my previous post. Perhaps my impression from the instructions (step 4) is incorrect.

  1. When the instructions refer to the "baseresourcename" what does that mean?
  2. Where exactly do I find that "baseresourcename" in the app registrations page?
  3. Are all of the highlighted sections in the below image that say "HERE" supposed to be the same URL? In my manifest.json, I'm adding the same value but maybe that's wrong.
  4. If they are supposed to all be the same value, where exactly do I find that URL in the app registrations page? Maybe I'm adding the wrong value here.

I'd also be happy to hop on a Teams call to show you our settings. Maybe that would be faster. Thanks again for your help.

image

JayPdsn commented 3 months ago

We are having a similar issue. My thought was the baseurl was created in step 4 (e.g. teocbaseresource - https://teocbaseresource.azurewebsites.net). Still troubleshooting...

image

On the other hand.. image

GitRomney commented 3 months ago

@JayPdsn Do you maybe want to create a new issue, to avoid confusion?

JayPdsn commented 3 months ago

I thought about creating a new incident, but didn't want to duplicate issues since we are having the exact same problem. I definitely can if that is preferable.

v-ajaysahu commented 3 months ago

@GitRomney , The base resource name is what you provided during the deployment to your Azure Subscription. If you are still finding it difficult, please provide your email address through GitHub (Please do not send it via email, as we will be unable to view it) and your available times so we can schedule an MS Teams call to troubleshoot the issue.

GitRomney commented 3 months ago

Thank you. We are available today between 10am and 12:30pm CDT, 1-2:30pm CDT, and 3-4:30pm CDT.

v-ajaysahu commented 3 months ago

@GitRomney , Following our discussion in the meeting, the SharePoint Name is incorrect. Kindly delete the resource group and redo the process using the correct name as specified in the deployment guide. https://github.com/OfficeDev/microsoft-teams-emergency-operations-center/wiki/Deployment-Guide

GitRomney commented 3 months ago

Thank you for your help today. Yes, when we got to step 1. in part 1 of the instructions, we included the full URL instead of just the last part, after "/sites/. We noticed some other things too. Doing some more testing and I'll report back here today or Monday with more details.

image

GitRomney commented 3 months ago

We seem to have the app working now. I'm not entirely sure what did it. Our Cloud Operations guy who makes the changes in Entra ID tells me he thinks this is what fixed it: "Our module defaults to disabling FTP/FTPS, but the ARM deployment had FTPS enabled on the App Services. Enabled FTPS on both App Services." Posting that here in case it's helpful to others.

v-ajaysahu commented 3 months ago

@GitRomney , Thank you for the update. As your issue has been resolved, I am closing this issue. Please feel free to add any further comments.

GitRomney commented 3 months ago

Would you agree that enabling FTPS is important? It isn't listed in the deployment document so just curious.

v-ajaysahu commented 3 months ago

@GitRomney , Yes, it is crucial because the app is being built and deployed into the App Service directly from GitHub. Moreover, this is included in the ARM template, and it is not required to be updated, so it was not mentioned in the deployment document.

JayPdsn commented 3 months ago

v-ajaysahu

Do you receive the email replies?

Jay Pedersen

Senior Enterprise Application Analyst

The Woodlands Township

281-210-3496

From: v-ajaysahu @.> Sent: Monday, July 1, 2024 9:41 AM To: OfficeDev/microsoft-teams-emergency-operations-center @.> Cc: Jay Pedersen @.>; Mention @.> Subject: [EXTERNAL]Re: [OfficeDev/microsoft-teams-emergency-operations-center] New Deployment of TEOC 3.1. Pane is blank upon upload (step 8) (Issue #210)

@GitRomneyhttps://github.com/GitRomney , Yes, it is crucial because the app is being built and deployed into the App Service directly from GitHub. Moreover, this is included in the ARM template, and it is not required to be updated, so it was not mentioned in the deployment document.

— Reply to this email directly, view it on GitHubhttps://github.com/OfficeDev/microsoft-teams-emergency-operations-center/issues/210#issuecomment-2200348028, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BJOFDPUZHPBDUXGQC6T2MBLZKFTCJAVCNFSM6AAAAABJZ53PACVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMBQGM2DQMBSHA. You are receiving this because you were mentioned.

This is an email from an EXTERNAL source. DO NOT click links or open attachments without positive sender verification of purpose. Never enter USERNAME, PASSWORD or sensitive information on linked pages from this email.