Incident URL

%3CLINGO-SUB%20id%3D%22lingo-sub-1003172%22%20slang%3D%22en-US%22%3EIncident%20URL%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1003172%22%20slang%3D%22en-US%22%3E%3CP%3EWhat%20is%20the%20URL%20to%20get%20to%20a%20specific%20Incident's%20Full%20Details%20page%3F%26nbsp%3B%20The%20URL%20I%20get%20from%20my%20browser%20only%20takes%20me%20to%20the%20listing%20of%20Incidents.%26nbsp%3B%20I%20thought%20I%20saw%20it%20listed%20here%20before%20but%20I%20cannot%20find%20it.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1015516%22%20slang%3D%22en-US%22%3ERe%3A%20Incident%20URL%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1015516%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F46875%22%20target%3D%22_blank%22%3E%40Gary%20Bushey%3C%2FA%3E%2C%20do%20you%20mean%20this%20%3CFONT%20style%3D%22background-color%3A%20%23ffffff%3B%22%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FAzure-Sentinel%2FURL-entity-type%2Fm-p%2F957193%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FAzure-Sentinel%2FURL-entity-type%2Fm-p%2F957193%3C%2FA%3E%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1015716%22%20slang%3D%22en-US%22%3ERE%3A%20Incident%20URL%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1015716%22%20slang%3D%22en-US%22%3ENo.%20I%20mean%20is%20there%20a%20URL%20that%20would%20take%20me%20directly%20to%20the%20page%20showing%20an%20Incident's%20full%20details.%20Would%20be%20very%20useful%20to%20put%20into%20Teams%20messages%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1015775%22%20slang%3D%22en-US%22%3ERE%3A%20Incident%20URL%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1015775%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F46875%22%20target%3D%22_blank%22%3E%40Gary%20Bushey%3C%2FA%3E%2C%20thank%20you%20for%20your%20feedback!%20Adding%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F2864%22%20target%3D%22_blank%22%3E%40Nicholas%20DiCola%20(SECURITY%20JEDI)%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1017640%22%20slang%3D%22en-US%22%3ERE%3A%20Incident%20URL%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1017640%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F293935%22%20target%3D%22_blank%22%3E%40Valon_Kolica%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F46875%22%20target%3D%22_blank%22%3E%40Gary%20Bushey%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3Ewe%20dont%20have%20a%20%22deep%20link%22%20exposed%20today.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1068970%22%20slang%3D%22en-US%22%3ERE%3A%20Incident%20URL%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1068970%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F46875%22%20target%3D%22_blank%22%3E%40Gary%20Bushey%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EGreat%20news%2C%20this%20has%20arrived!%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F162042iB7B50E16A47EF97A%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20alt%3D%22clipboard_image_0.png%22%20title%3D%22clipboard_image_0.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENicholas%20(I%20can't%26nbsp%3B%40%20you%2C%20I%20get%20an%20%22invalid%20HTML%22%20error%20when%20I%20try%20to%20post)%26nbsp%3Bis%20there%20somewhere%20that%20release%20notes%20of%20changes%20like%20this%20are%20posted%3F%20Or%20even%20better%20a%20roadmap%20so%20we%20know%20what's%20coming%3F%20Knowing%20this%20was%20coming%20would%20have%20saved%20us%20a%20lot%20of%20time%20last%20week.%20The%20biggest%20thing%20we're%20eager%20for%20is%20when%20are%20Sentinel%20Incidents%20coming%20to%20the%20Graph%20API%2C%20we're%20investing%20a%20lot%20of%20time%20in%20making%20Logic%20Apps%20so%20we%20can%20interact%20with%20Incidents%20via%20the%20API%20from%20ServiceNow%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1069165%22%20slang%3D%22en-US%22%3ERE%3A%20Incident%20URL%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1069165%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F490732%22%20target%3D%22_blank%22%3E%40mevops%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3Eweird%20on%20the%26nbsp%3B%40%20...%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3Ewe%20normally%20announce%20things%20in%20the%20what%20new%20blade%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F162058i19C847CBB5EAF55F%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20alt%3D%22clipboard_image_0.png%22%20title%3D%22clipboard_image_0.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ENot%20everything%20will%20be%20announced%20as%20some%20are%20minor%20features.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1085875%22%20slang%3D%22en-US%22%3ERe%3A%20Incident%20URL%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1085875%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F46875%22%20target%3D%22_blank%22%3E%40Gary%20Bushey%3C%2FA%3E%26nbsp%3BIf%20an%20incident%20is%20triggered%20by%20a%20Microsoft%20Service%20data%20connector%20%26gt%3B%20Incidents%20%26gt%3B%20View%20Full%20Details%20%26gt%3B%20ALERT%20ID%20%26gt%3B%20ExtendedLinks%20should%20contain%20two%20Href%20links%20-%20one%20might%20be%20the%20security%20policy%20ID%20and%20the%20other%20the%20Security%20Alert%20ID%20-%20if%20you%20navigate%20to%20the%20URL%20in%20the%20Security%20alert%20ID%20is%20this%20the%20link%20you%20were%20looking%20for%3F%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1085902%22%20slang%3D%22en-US%22%3ERE%3A%20Incident%20URL%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1085902%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F490732%22%20target%3D%22_blank%22%3E%40mevops%3C%2FA%3E%26nbsp%3BHave%20you%20also%20found%20that%20this%20Incident%20Link%20is%20a%20bit%20useless%3F%20All%20it%20does%20is%20link%20you%20to%20the%20exact%20same%20page%20you%20would%20receive%20if%20you%20click%20the%20'View%20full%20details'%20button%20underneath.%20It%20would%20be%20much%20more%20useful%20if%20it%20copied%20out%20the%20Microsoft%20Service%20alert%20href%20from%20the%20extended%20properties%20in%20the%20alert.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1086987%22%20slang%3D%22en-US%22%3ERE%3A%20Incident%20URL%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1086987%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F504157%22%20target%3D%22_blank%22%3E%40jcheal%3C%2FA%3E%26nbsp%3Bwhile%20I%20think%20Sentinel%20does%20indeed%20need%20a%20link%20back%20to%20the%20original%20Alert%2C%20if%20there%20is%20one%2C%20in%20this%20case%20the%20URL%20provided%20does%20just%20what%20I%20wanted%20it%20to.%26nbsp%3B%20I%20wanted%20to%20be%20able%20to%20put%20this%20URL%20into%20a%20Team's%20message%20so%20that%20users%20had%20a%20quick%20and%20easy%20way%20to%20get%20back%20to%20the%20Incident.%26nbsp%3B%20%26nbsp%3BNow%20it%20just%20needs%20to%20show%20up%20as%20a%20field%20in%20the%20Logic%20App's%20connector%20%3A)%3C%2Fimg%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1150976%22%20slang%3D%22en-US%22%3ERE%3A%20Incident%20URL%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1150976%22%20slang%3D%22en-US%22%3ESorry%20for%20the%20delay%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F504157%22%20target%3D%22_blank%22%3E%40jcheal%3C%2FA%3E%2C%20didn't%20spot%20this.%3CBR%20%2F%3E%3CBR%20%2F%3EIt's%20actually%20perfect%20for%20what%20we%20needed%20it%20for!%20We%20integrate%20Sentinel%20Incidents%20into%20our%20ServiceNow%20platform.%20We%20specifically%20sync%20Incidents%2C%20not%20Alerts%2C%20so%20that%20we%20don't%20lose%20all%20the%20aggregation%20power%20etc%20that%20Sentinel%20has%20in%20dealing%20with%20Alerts.%20We%20needed%20a%20way%20to%20get%20back%20to%20the%20Sentinel%20Incident%20from%20the%20ServiceNow%20platform%20though.%3CBR%20%2F%3E%3CBR%20%2F%3EThis%20link%20has%20allowed%20us%20to%20put%20a%20button%20on%20the%20ServiceNow%20Incident%20that%20takes%20the%20agent%20directly%20to%20the%20related%20Incident%20in%20Sentinel.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1151304%22%20slang%3D%22en-US%22%3ERE%3A%20Incident%20URL%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1151304%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F490732%22%20target%3D%22_blank%22%3E%40mevops%3C%2FA%3E%26nbsp%3BI%20wrote%20a%20blog%20post%20about%20adding%20this%20to%20an%20Incident.%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fwww.garybushey.com%2F2020%2F01%2F24%2Faddin-the-mcas-alert-url-to-a-sentinel-incident-using-powershell%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.garybushey.com%2F2020%2F01%2F24%2Faddin-the-mcas-alert-url-to-a-sentinel-incident-using-powershell%2F%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1384654%22%20slang%3D%22en-US%22%3ERE%3A%20Incident%20URL%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1384654%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F46875%22%20target%3D%22_blank%22%3E%40Gary%20Bushey%3C%2FA%3E%26nbsp%3B%20-%20were%20you%20able%20to%20find%20a%20way%20to%26nbsp%3B%3CSPAN%3Ereference%20this%20URL%20in%20a%20LogicApp%20for%20posting%20into%20Teams%20or%20ServiceNow%3F%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1421901%22%20slang%3D%22en-US%22%3ERe%3A%20Incident%20URL%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1421901%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F504157%22%20target%3D%22_blank%22%3E%40jcheal%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%40%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F2864%22%20target%3D%22_blank%22%3ENicholas%20DiCola%20(SECURITY%20JEDI)%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAs%20a%20Security%20Analyst%20I%20prefer%20to%20go%20to%20the%20original%20Dashboard%20(e.g.%20in%20case%20I%20receive%20an%20MCAS%20ord%20Defender%20Alert%20in%20Sentinel%2C%20I%20like%20to%20jump%20out%20of%20Sentinel%20and%20go%20to%20the%20original%20Dashboard%2C%20as%20I%20have%20more%20analysis%20option%20there).%20Is%20there%20an%20easy%20way%20to%20navigate%20to%20the%20Source%20Dashboard%3F%20I%20think%20it%20is%20not%20so%20user%20friendly%20to%20search%20for%20the%20url%20in%20the%20logs%20(Extended%20Links).%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1423588%22%20slang%3D%22en-US%22%3ERe%3A%20Incident%20URL%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1423588%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F681519%22%20target%3D%22_blank%22%3E%40CurlX%3C%2FA%3E%26nbsp%3BI%20would%20suggest%20adding%20this%20to%20the%20Azure%20Sentinel%20feedback%20site%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ffeedback.azure.com%2Fforums%2F920458-azure-sentinel%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Ffeedback.azure.com%2Fforums%2F920458-azure-sentinel%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1425915%22%20slang%3D%22en-US%22%3ERe%3A%20Incident%20URL%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1425915%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F46875%22%20target%3D%22_blank%22%3E%40Gary%20Bushey%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EGreat%20point.%20I%20already%20found%20it%20written%20by%20someone%20else%20%3A)%3C%2Fimg%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ffeedback.azure.com%2Fforums%2F920458-azure-sentinel%2Fsuggestions%2F39285991-improve-incident-link-reference%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Ffeedback.azure.com%2Fforums%2F920458-azure-sentinel%2Fsuggestions%2F39285991-improve-incident-link-reference%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Super Contributor

What is the URL to get to a specific Incident's Full Details page?  The URL I get from my browser only takes me to the listing of Incidents.  I thought I saw it listed here before but I cannot find it.

15 Replies
Highlighted
Highlighted
No. I mean is there a URL that would take me directly to the page showing an Incident's full details. Would be very useful to put into Teams messages
Highlighted

Hi @Gary Bushey, thank you for your feedback! Adding @Nicholas DiCola (SECURITY JEDI) 

Highlighted

@Valon_Kolica 

@Gary Bushey 

 

we dont have a "deep link" exposed today.

 

 

Highlighted

@Gary Bushey 

Great news, this has arrived!

clipboard_image_0.png

 

 

Nicholas (I can't @ you, I get an "invalid HTML" error when I try to post) is there somewhere that release notes of changes like this are posted? Or even better a roadmap so we know what's coming? Knowing this was coming would have saved us a lot of time last week. The biggest thing we're eager for is when are Sentinel Incidents coming to the Graph API, we're investing a lot of time in making Logic Apps so we can interact with Incidents via the API from ServiceNow

Highlighted

@mevops 

weird on the @ ...

 

we normally announce things in the what new blade

clipboard_image_0.png

 

Not everything will be announced as some are minor features.

Highlighted

@Gary Bushey If an incident is triggered by a Microsoft Service data connector > Incidents > View Full Details > ALERT ID > ExtendedLinks should contain two Href links - one might be the security policy ID and the other the Security Alert ID - if you navigate to the URL in the Security alert ID is this the link you were looking for? 

Highlighted

@mevops Have you also found that this Incident Link is a bit useless? All it does is link you to the exact same page you would receive if you click the 'View full details' button underneath. It would be much more useful if it copied out the Microsoft Service alert href from the extended properties in the alert. 

Highlighted

@jcheal while I think Sentinel does indeed need a link back to the original Alert, if there is one, in this case the URL provided does just what I wanted it to.  I wanted to be able to put this URL into a Team's message so that users had a quick and easy way to get back to the Incident.   Now it just needs to show up as a field in the Logic App's connector :)

 

Highlighted
Sorry for the delay @jcheal, didn't spot this.

It's actually perfect for what we needed it for! We integrate Sentinel Incidents into our ServiceNow platform. We specifically sync Incidents, not Alerts, so that we don't lose all the aggregation power etc that Sentinel has in dealing with Alerts. We needed a way to get back to the Sentinel Incident from the ServiceNow platform though.

This link has allowed us to put a button on the ServiceNow Incident that takes the agent directly to the related Incident in Sentinel.
Highlighted
Highlighted

@Gary Bushey  - were you able to find a way to reference this URL in a LogicApp for posting into Teams or ServiceNow?

Highlighted

@jcheal 

Nicholas DiCola (SECURITY JEDI)

 

As a Security Analyst I prefer to go to the original Dashboard (e.g. in case I receive an MCAS ord Defender Alert in Sentinel, I like to jump out of Sentinel and go to the original Dashboard, as I have more analysis option there). Is there an easy way to navigate to the Source Dashboard? I think it is not so user friendly to search for the url in the logs (Extended Links). 

 

 

Highlighted

@CurlX I would suggest adding this to the Azure Sentinel feedback site: https://feedback.azure.com/forums/920458-azure-sentinel

 

 

Highlighted