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
95 stars 40 forks source link

Customer needs help #133

Closed jugaraka closed 1 year ago

jugaraka commented 1 year ago

I have a Microsoft customer who needs Support help from the TEOC team, and this is impacting C-suite, 911, Fire dept and other hospital Executive's for case 2308070040008132 at [PPI]. Business Issue: Users at [PPI] are not able to create new incidents report using Emergency Operation Center (TEOC) and this is now directly impacting the health and safety of a hospital. Please advise.

v-prigunasek commented 1 year ago

Hi @jugaraka ,

Can you please share us the console logs and the network trace to figure out the root cause of the error they are receiving in TEOC app?

To get a console logs, please try to access the TEOC application in the browser version of MS Teams and open Developer tools from browser (or press Ctrl + Shift + I , this will open the console window) and replicate the error by creating new incident then right click on the logs to Save it as a log file.

image

image

To get Network trace, Open the network window and Export the log trace as HAR file.

image

Please share us these logs and HAR files to further investigate on this issue. Thanks.

jugaraka commented 1 year ago

Thank you for the help here. We are on call with the customer currently/Troubleshooting at this time.

Justin J. Garakanian Incident Manager - US Public Sector @.**@.> Hours: M-F 7 am to 4 pm - Central Office: +1 (469) 775-0839 @.***

Microsoft Services Support: https://serviceshub.microsoft.comhttps://serviceshub.microsoft.com/ Support (24/7): +1 (800) 936-3100 Support (US NAT): +1 (800) 936-3200 Support (GCC High): +1 (877) 966-7787

From: v-prigunasek @.> Sent: Thursday, August 17, 2023 10:50 AM To: OfficeDev/microsoft-teams-emergency-operations-center @.> Cc: Justin Garakanian @.>; Mention @.> Subject: Re: [OfficeDev/microsoft-teams-emergency-operations-center] Customer needs help (Issue #133)

Hi @jugarakahttps://github.com/jugaraka ,

Can you please share us the console logs and the network trace to figure out the root cause of the error they are receiving in TEOC app?

To get a console logs, please try to access the TEOC application in the browser version of MS Teams and open Developer tools from browser (or press Ctrl + Shift + I , this will open the console window) and replicate the error by creating new incident then right click on the logs to Save it as a log file.

[image]https://user-images.githubusercontent.com/98514691/261363168-05eee429-a29a-45c1-8dea-32a0cde44b77.png

[image]https://user-images.githubusercontent.com/98514691/261363239-9eb160cf-85ff-45b9-b2b6-6871b1407041.png

To get Network trace, Open the network window and Export the log trace as HAR file.

[image]https://user-images.githubusercontent.com/98514691/261363280-19c1d2d4-b307-479e-acfe-1bf372524103.png

Please share us these logs and HAR files to further investigate on this issue. Thanks.

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

v-prigunasek commented 1 year ago

In the call with customer, the issue was identified, and it was due to the group creation setting in the tenant that is set to NO (Azure Portal --> Groups --> Settings-->General -> Users can create Microsoft 365 groups in Azure portals, API or PowerShell" )

To workaround this, asked them to follow this documentation to Manage who can create Microsoft 365 Groups | Microsoft Learn.

Issue was resolved after implementing the solution provided in the documentation. Hence closing this ticket.