Microsoft HoloLens 2 and mixed reality bridge physical reality and digital experiences

Microsoft HoloLens 2 and mixed reality bridge physical reality and digital experiences

by | Feb 23, 2022 | Dynamics 365, Microsoft 365, Technology

This article is contributed. See the original author and article here.

Across industries, companies are finding practical ways to bridge physical reality and digital experiences using hands-free headsets and augmented reality solutions to inform decisions and action on insights produced by smart, connected solutions.

Mixed realitya set of technologies that superimposes digital data and images in the physical worldbrings new opportunities that have become instrumental to how we tap into unique real-world, human capabilities. This technology is becoming more widely used across organizations today and has proven to be transformative to task performance, learning and retention, and collaboration. In fact, the augmented and virtual reality market is expected to reach $372.1 billion by the end of 2022, and swell to $542.8 billion by the end of 2025 according to new data from the IDC.1

Microsoft’s comprehensive ecosystem of mixed reality solutions such as Microsoft HoloLens 2, Microsoft Dynamics 365 Remote Assist, and Microsoft Dynamics 365 Guides are helping organizations optimize operations, reduce downtime, accelerate onboarding and upskilling, and decrease costs with more precise, efficient hands-free work.

Microsoft HoloLens 2 and mixed reality solutions are driving material ROI across industries

Based on the Microsoft-commissioned Forrester Total Economic Impact (TEI) report, Microsoft HoloLens 2 is delivering 177 percent return on investment (ROI) and a net present value (NPV) of $7.6 million over three years with a payback of 13 months.2 Customers across leading industries are realizing significant value from deploying mixed reality solutions in their most common, critical work scenarios.

Manufacturing

Manufacturing companies deploying Microsoft HoloLens 2 and mixed reality applications to train their workforces, accelerate employee proficiency, and build more agile factories. Using Microsoft mixed reality, Manufacturers reduced training time by 75 percent, at an average savings of $30 per labor hour.2

Manufacturers reduced training time by 75 percent, at an average savings of 30 dollars per labor hour.

Common scenarios in which manufacturers benefit from mixed reality on Microsoft HoloLens 2:

  1. Guided assembly and training: Empower employees to learn new skills and complex assembly tasks with holographic step-by-step instructions, no instructor necessary.  
  2. Remote inspection and audits: Enable remote employees to solve business problems in real time, using 3D annotations to access, share, and bring critical information into view.
  3. Connected field service: Connect field technicians with remote experts to collaborate seamlessly, heads-up and hands-free with content capture abilities, interactive annotations, and contextual data overlays.

“When you describe a problem, imagine that we are speaking different languages. When you explain it, someone on the other side may not understand precisely what’s happening, but when you show it in real time with the HoloLens, people understand.”Eaton Vehicle Group. Read more about the Eaton Vehicle Group customer story.

Education

Educators are turning to Microsoft HoloLens 2 and mixed reality applications to help students embrace a new way of learning. For example, education institutions reduced 520 annual hours of instruction per expert by 15 percent.2

Education institutions reduced 520 annual hours of instruction per expert by 15 percent.

Common scenarios in which educators benefit from mixed reality on Microsoft HoloLens 2:

  1. Augmented teaching: Captivate students and bring education to life with impressionable, high-impact 3D visualization models that enable virtual collaboration and instruction.
  2. Experiential learning: Enable educators to build an experience-based lesson plan, integrating textbook concepts into physical environments to create a simple “learn by doing” approach for studentshands-on and unmediated.
  3. Scaled learning and research: Develop a scalable research collaboration model that improves efficiency of research, lab work, and medical training.

“We did a trial back with our medical students. The students that had been in the HoloLens lab scored 50 percent better compared to the rest of the med school class.”Case Western. Read more about the Case Western customer story.

Healthcare

Mixed reality is empowering providers, payors, and health science experts to reimagine healthcare by accelerating diagnoses, reducing time-to-care, and enabling personalization. Using Microsoft mixed reality, healthcare providers reduced average consumables by 80%, saving $4,000 per trainee.2

Healthcare providers reduced average consumables by 80 percent, saving 4,000 dollars per trainee.

Common scenarios in which healthcare providers benefit from mixed reality on Microsoft HoloLens 2:

  1. Holographic patient consultation: Enable healthcare providers to project 3D holographic visualizations of patients’ internal systems that provide procedural understandingbuilding confidence in upcoming procedures and/or treatments.
  2. Remote expert consultation: Support remote consultation and enable medical staff to consult colleagues with heads-up and hands-free through an interactive collaborative experience from anywhere in the world.
  3. Training simulations: Train medical staff with holographic step-by-step guidance without subject matter experts being physically present.

“Using Dynamics 365 Remote Assist, doctors wearing HoloLens, can hold “hands-free” and “heads-up” Teams video calls with colleagues and experts anywhere in the world. They can receive advice, interacting with the caller and the patient at the same time, while medical notes and X-rays can also be placed alongside the call in the wearer’s field of view.”Imperial College Healthcare NHS Trust. Read more about the Imperial College Healthcare NHS Trust customer story.

Architecture, engineering, and construction

With Mixed Reality, architecture, engineering, and construction (AEC) firms are empowered to overcome design, modeling, collaboration, and building site challenges to enhance project quality, decision-making, improve productivity. For example, AEC firms have reduced rework by 75 percent, saving $44 per hour.2

A E C firms have reduced rework by 75 percent, saving 44 dollars per hour.

Common scenarios in which AEC organizations benefit from mixed reality on Microsoft HoloLens 2:

  1. Clash detection: Enable onsite workers to preemptively identify issues, detect clashes, and gain buy-in of onsite workers and key stakeholders with overlay designs on physical locations. This mitigates late-stage design changes that could result in rework, budget overrun, and project delays.
  2. 3D plan and model demonstrations: Empower project leaders, designers, and engineers and improve customer service and sales with 3D demonstration and immersive visualizations.
  3. Self-guided learning: Equip onsite workers to view task instructions, essential data, and model visualizations while in the flow of work, increasing speed, quality, and safety.           

“We use Dynamics 365 Remote Assist on HoloLens 2 to work more effectively and share expertise at critical milestones. This not only saves us money but also helps us construct datacenters for our customers more quickly.”Microsoft. Read the full customer story.

The Forrester TEI study validates how mixed reality solutions on Microsoft HoloLens 2 are empowering enterprises across industries to achieve more. We believe these technologies have offered not only innovative results, but long-term and sustainable solutions for training, remote collaboration, inspections and audits, field service, and more.

Next steps

We look forward to continuing this blog series with a deep dive spotlight on each of these leading industries. In the meantime, learn more about mixed reality applications on Microsoft HoloLens 2 and get started today:

Sources:

  1. Worldwide Quarterly Wearable Device Tracker, IDC, 2022
  2. The Total Economic Impact Of Mixed Reality Using Microsoft HoloLens 2 Report, Forrester, 2022

The post Microsoft HoloLens 2 and mixed reality bridge physical reality and digital experiences appeared first on Microsoft Dynamics 365 Blog.

Brought to you by Dr. Ware, Microsoft Office 365 Silver Partner, Charleston SC.

New Sandworm Malware Cyclops Blink Replaces VPNFilter

New Sandworm Malware Cyclops Blink Replaces VPNFilter

by | Feb 23, 2022 | Security, Technology

This article is contributed. See the original author and article here.

Summary

The Sandworm actor, which the United Kingdom and the United States have previously attributed to the Russian GRU, has replaced the exposed VPNFilter malware with a new more advanced framework.

The United Kingdom’s (UK) National Cyber Security Centre (NCSC), the Cybersecurity and Infrastructure Security Agency (CISA), the National Security Agency (NSA), and the Federal Bureau of Investigation (FBI) in the U.S. have identified that the actor known as Sandworm or Voodoo Bear is using a new malware, referred to here as Cyclops Blink. The NCSC, CISA, and the FBI have previously attributed the Sandworm actor to the Russian General Staff Main Intelligence Directorate’s Russian (GRU’s) Main Centre for Special Technologies (GTsST). The malicious cyber activity below has previously been attributed to Sandworm:

Cyclops Blink appears to be a replacement framework for the VPNFilter malware exposed in 2018, and which exploited network devices, primarily small office/home office (SOHO) routers and network attached storage (NAS) devices.

This advisory summarizes the VPNFilter malware it replaces, and provides more detail on Cyclops Blink, as well as the associated tactics, techniques and procedures (TTPs) used by Sandworm. An NCSC malware analysis report on Cyclops Blink is also available.

It also provides mitigation measures to help organizations defend against malware.

Click here for a PDF version of this report.

Technical Details

VPNFilter

The malware was first exposed in 2018

A series of articles published by Cisco Talos in 2018 describes VPNFilter and its modules in detail. VPNFilter was deployed in stages, with most functionality in the third-stage modules. These modules enabled traffic manipulation, destruction of the infected host device, and likely enabled downstream devices to be exploited. They also allowed monitoring of Modbus SCADA protocols, which appears to be an ongoing requirement for Sandworm, as also seen in their previous attacks against ICS networks.

VPNFilter targeting was widespread and appeared indiscriminate, with some exceptions: Cisco Talos reported an increase of victims in Ukraine in May 2018. Sandworm also deployed VPNFilter against targets in the Republic of Korea before the 2018 Winter Olympics. 

In May 2018, Cisco Talos published the blog that exposed VPNFilter and the U.S. Department of Justice linked the activity to Sandworm and announced efforts to disrupt the botnet.

Activity since its exposure 

A Trendmicro blog in January 2021 detailed residual VPNFilter infections and provided data which showed that although there had been a reduction in requests to a known C2 domain, there was still more than a third of the original number of first-stage infections.

Sandworm has since shown limited interest in existing VPNFilter footholds, instead preferring to retool.

Cyclops Blink

Active since 2019

The NCSC, CISA, the FBI, and NSA, along with industry partners, have now identified a large-scale modular malware framework (T1129) which is targeting network devices. The new malware is referred to here as Cyclops Blink and has been deployed since at least June 2019, fourteen months after VPNFilter was disrupted. In common with VPNFilter, Cyclops Blink deployment also appears indiscriminate and widespread.

The actor has so far primarily deployed Cyclops Blink to WatchGuard devices, but it is likely that Sandworm would be capable of compiling the malware for other architectures and firmware.

Note: Note that only WatchGuard devices that were reconfigured from the manufacturer default settings to open remote management interfaces to external access could be infected

Malware overview 

The malware itself is sophisticated and modular with basic core functionality to beacon (T1132.002) device information back to a server and enable files to be downloaded and executed. There is also functionality to add new modules while the malware is running, which allows Sandworm to implement additional capability as required.

The NCSC has published a malware analysis report on Cyclops Blink which provides more detail about the malware.

Post exploitation 

Post exploitation, Cyclops Blink is generally deployed as part of a firmware ‘update’ (T1542.001). This achieves persistence when the device is rebooted and makes remediation harder.

Victim devices are organized into clusters and each deployment of Cyclops Blink has a list of command and control (C2) IP addresses and ports that it uses (T1008). All the known C2 IP addresses to date have been used by compromised WatchGuard firewall devices. Communications between Cyclops Blink clients and servers are protected under Transport Layer Security (TLS) (T1071.001), using individually generated keys and certificates. Sandworm manages Cyclops Blink by connecting to the C2 layer through the Tor network.

Mitigations

Cyclops Blink persists on reboot and throughout the legitimate firmware update process. Affected organizations should therefore take steps to remove the malware. 

WatchGuard has worked closely with the FBI, CISA, NSA and the NCSC, and has provided tooling and guidance to enable detection and removal of Cyclops Blink on WatchGuard devices through a non-standard upgrade process. Device owners should follow each step in these instructions to ensure that devices are patched to the latest version and that any infection is removed.

The tooling and guidance from WatchGuard can be found at: https://detection.watchguard.com/.

In addition:

  • If your device is identified as infected with Cyclops Blink, you should assume that any passwords present on the device have been compromised and replace them (see NCSC password guidance for organizations.
  • You should ensure that the management interface of network devices is not exposed to the internet.

Indicators of Compromise

Please refer to the accompanying Cyclops Blink malware analysis report for indicators of compromise which may help detect this activity. 

MITRE ATT&CK®

This advisory has been compiled with respect to the MITRE ATT&CK® framework, a globally accessible knowledge base of adversary tactics and techniques based on real-world observations.

Tactic

Technique

Procedure

Initial Access

T1133

External Remote Services

The actors most likely deploy modified device firmware images by exploiting an externally available service

Execution

T1059.004

Command and Scripting Interpreter: Unix Shell

Cyclops Blink executes downloaded files using the Linux API

Persistence

T1542.001

Pre-OS Boot: System Firmware

Cyclops Blink is deployed within a modified device firmware image

T1037.004

Boot or Logon Initialization Scripts: RC Scripts

Cyclops Blink is executed on device startup, using a modified RC script
Defense Evasion

T1562.004

Impair Defenses: Disable or Modify System Firewall

Cyclops Blink modifies the Linux system firewall to enable C2 communication
 

T1036.005

Masquerading: Match Legitimate Name or Location

Cyclops Blink masquerades as a Linux kernel thread process

Discovery

T1082

System Information Discovery

Cyclops Blink regularly queries device information

Command and Control

T1090

Proxy

T1132.002

Data Encoding: Non-Standard Encoding

Cyclops Blink command messages use a custom binary scheme to encode data

T1008

Fallback Channels

Cyclops Blink randomly selects a C2 server from contained lists of IPv4 addresses and port numbers

T1071.001

Application Layer Protocol: Web Protocols

Cyclops Blink can download files via HTTP or HTTPS

T1573.002

Encrypted Channel: Asymmetric Cryptography

Cyclops Blink C2 messages are individually encrypted using AES-256-CBC and sent underneath TLS

T1571

Non-Standard Port

The list of port numbers used by Cyclops Blink includes non-standard ports not typically associated with HTTP or HTTPS traffic
Exfiltration

T1041

Exfiltration Over C2 Channel

Cyclops Blink can upload files to a C2 server

A Cyclops Blink infection does not mean that an organization is the primary target, but it may be selected to be, or its machines could be used to conduct attacks.

Organizations are advised to follow the mitigation advice in this advisory to defend against this activity, and to refer to indicators of compromise (not exhaustive) in the Cyclops Blink malware analysis report to detect possible activity on networks. 

UK organizations affected by the activity outlined in should report any suspected compromises to the NCSC at https://report.ncsc.gov.uk/.

Further Guidance

A variety of mitigations will be of use in defending against the malware featured in this advisory:

About This Document

This advisory is the result of a collaborative effort by United Kingdom’s National Cyber Security Centre (NCSC), the United States’ National Security Agency (NSA), the Federal Bureau of Investigation (FBI), and Department of Homeland Security (DHS) Cybersecurity and Infrastructure Security Agency (CISA). 

CISA, FBI, and NSA agree with this attribution and the details provided in the report.

This advisory has been compiled with respect to the MITRE ATT&CK® framework, a globally accessible knowledge base of adversary tactics and techniques based on real-world observations. 

Disclaimers

This report draws on information derived from NCSC and industry sources. Any NCSC findings and recommendations made have not been provided with the intention of avoiding all risks and following the recommendations will not remove all such risk. Ownership of information risks remains with the relevant system owner at all times.

DISCLAIMER OF ENDORSEMENT: The information and opinions contained in this document are provided “as is” and without any warranties or guarantees. Reference herein to any specific commercial products, process, or service by trade name, trademark, manufacturer, or otherwise, does not constitute or imply its endorsement, recommendation, or favoring by the United States Government, and this guidance shall not be used for advertising or product endorsement purposes.

For NSA client requirements or general cybersecurity inquiries, contact the Cybersecurity Requirements Center at 410-854-4200 or Cybersecurity_Requests@nsa.gov.

Contact Information

To report suspicious or criminal activity related to information found in this joint Cybersecurity Advisory:

U.S. organizations contact your local FBI field office at fbi.gov/contact-us/field-offices, or the FBI’s 24/7 Cyber Watch (CyWatch) at (855) 292-3937 or by email at CyWatch@fbi.gov. When available, please include the following information regarding the incident: date, time, and location of the incident; type of activity; number of people affected; type of equipment used for the activity; the name of the submitting company or organization; and a designated point of contact. To request incident response resources or technical assistance related to these threats, contact CISA at Central@cisa.gov.

Australian organizations should report incidents to the Australian Signals Directorate’s (ASD’s) ACSC via cyber.gov.au or call 1300 292 371 (1300 CYBER 1).

U.K. organizations should report a significant cyber security incident: ncsc.gov.uk/report-an-incident (monitored 24 hrs) or for urgent assistance, call 03000 200 973.

Revisions

February 23, 2022: Initial Version

This product is provided subject to this Notification and this Privacy & Use policy.

Build a trusted authentication service for Azure Communication Services using Azure Active Directory

Build a trusted authentication service for Azure Communication Services using Azure Active Directory

by | Feb 22, 2022 | Technology

This article is contributed. See the original author and article here.

We’re releasing a new service sample to help you build secure voice, video, and chat applications. This sample provides you with an easy to deploy, trusted authentication service to generate Azure Communication Services identities and access tokens. It is available for both node.js and C#. 


 


Azure Communication Services is designed with a bring-your-own-identity (BYOI) architecture. Identity and sign-on experiences are core to your unique application. Apps like LinkedIn have their own end-user identity system, while healthcare apps may use identity providers as part of existing middleware, and other apps may use 3rd party providers such as Facebook. 


 


We’ve designed the ACS identity system to be simple and generic, so you have the flexibility to build whatever experience you want. 


 


This new sample uses Azure App Service to authenticate users with Azure Active Directory (AAD), maps those users to ACS identities using Graph as storage, and finally generates ACS tokens when needed. We chose AAD for this sample because it’s a popular access management back-end, recognized for its security and scalability. It also integrates with 3rd party identity providers and OpenID interfaces. But you can use this sample as a launching point for integrating whatever identity provider or external system you want. 


 


The sample provides developers a turn-key service which uses the Azure Communication Service Identity SDK to create and delete users, and generate, refresh, and revoke access tokens.  The data flows for this sample are diagrammed below, but there is a lot more detail in GitHub with both node.js and C# repositories.  An Azure Resource Manager (ARM) template is provided that generates the Azure subscription and automate deployment with a few clicks. 


ddematheu_0-1644947264485.png


 


This identity service is only one component of a calling or chat application. Samples and documentation for other components and the underlying APIs are below. 


 
















Concept 

SDKs 

Samples

Identity


Calling


Chat

UI Library 


Calling


Chat

Authentication Service 


Calling Client 


Chat Client 

 


Please hit us up in the comments or Microsoft Q&A if you have questions about building apps! 


 

The top frauds of 2021

The top frauds of 2021

by | Feb 22, 2022 | Security

This article was originally posted by the FTC. See the original article here.

Every year, people report fraud, identity theft, and bad business practices to the FTC and its law enforcement partners. In 2021, 5.7 million people filed reports and described losing more than $5.8 billion to fraud — a $2.4 billion jump in losses in one year. You can learn about the types of fraud, identity theft, and marketplace issues people reported by state, and how scammers took payment — including $750 million in cryptocurrency — in the FTC’s new Consumer Sentinel Network Data Book. Here are some of the highlights:

  • More than 2.8 million people reported spotting a fraud, and one in four said they also lost money. Their combined losses were over $5.8 billion. Imposter scams, when someone pretended to be a trusted person or business, led to losses of $2.3 billion.
  • Almost 600,000 people filed reports about credit bureaus in 2021, an increase of more than 80 percent over the previous year. This jump in reports made credit bureaus, information furnishers, and report users the #3 most-reported category of 2021, behind imposter scams (#2) and identity theft (#1).
  • People ages 20-29 reported losing money to fraud more often than people ages 80 and over. While younger people lost money 41 percent of the time they experienced fraud, older adults lost money only 17 percent of the time. But when older people did lose money, they lost a median amount of $1,500, or three times the median amount younger people lost.

If you spot a scam, please report it to ReportFraud.ftc.gov.

Brought to you by Dr. Ware, Microsoft Office 365 Silver Partner, Charleston SC.

Tutorial: Publish Azure Static Web Apps with Bitbucket

Tutorial: Publish Azure Static Web Apps with Bitbucket

by | Feb 21, 2022 | Technology

This article is contributed. See the original author and article here.

In this tutorial, you learn to: 



  • Set up an Azure Static Web Apps site for a Vanilla API sample app

  • Create a Bitbucket Pipeline to build and publish a static web app 


Prerequisites 



  • Active Azure account: If you don’t have one, you can create an account for free. 

  • Bitbucket project: If you don’t have one, you can create a project for free. 

    • Bitbucket includes Pipelines. If you haven’t created a pipeline before, you first have to enable two-step verification for your Bitbucket account.

    • You can add SSH Keys using the steps here 




NOTE – The static web app Pipeline Task currently only works on Linux machines. When running the pipeline mentioned below, please ensure it is running on a Linux VM.

Create a static web app project in Bitbucket 


 


NOTE – If you have an existing app in your repository, you may skip to the next section.


  • After creating a new project, select Create repository and then click on Import repository.


 

RupaReddy_2-1645095212689.jpeg



  • Select Import repository to import the sample application. 


RupaReddy_8-1643803948840.png



Create a static web app 



  • Navigate to the Azure portal. 

  • Select Create a Resource. 

  • Search for Static Web Apps. 

  • Select Static Web Apps. 

  • Select Create. 

  • Create a new static web app with the following values. 










































                          Setting 

                                       Value 

Subscription 

Your Azure subscription name. 

Resource Group 

Select an existing group name, or create a new one. 

Name 

Enter myBitbucketApp. 

Hosting plan type 

Select Free. 

Region 

Select a region closest to you. 

Source 

Select Other. 

 

 

RupaReddy_9-1643803974940.png



  • Select Review + create 

  • Select Create. 

  • Once the deployment is successful, select Go to resource. 

  • Select Manage deployment token. 

  • Copy the deployment token and paste the deployment token value into a text editor for use in another screen. 


NOTE – This value is set aside for now because you’ll copy and paste more values in coming steps. 

 


 

RupaReddy_3-1645095672870.png


 


Create the Pipeline in Bitbucket 



  • Navigate to the repository in Bitbucket that was created earlier. 

  • Select Pipelines on the left menu. 


  • Ensure that you have enabled two-step verification for your bitbucket account.



  • Select Create your first pipeline. 


 

RupaReddy_12-1643804053501.png


 



  • In the Create your first pipeline screen, select Starter pipeline. 


RupaReddy_13-1643804086292.png


 



  • Copy the following YAML and replace the generated configuration in your pipeline with this code.

    pipelines:
  branches:
   main:
    - step: 
        name: Deploy to test
        deployment: test
        script:
          - pipe: microsoft/azure-static-web-apps-deploy:dev
            variables:
                APP_LOCATION: '$BITBUCKET_CLONE_DIR/src'
                API_LOCATION: '$BITBUCKET_CLONE_DIR/api'
                OUTPUT_LOCATION: '$BITBUCKET_CLONE_DIR'
                API_TOKEN: $deployment_token​

                                           



NOTE –  If you are not using the sample app, the values for  APP_LOCATION, API_LOCATION, and OUTPUT_LOCATION  need to change to match the values in your application. 
Note that you have to give the values for  APP_LOCATION, API_LOCATION, and OUTPUT_LOCATIONonly after  $BITBUCKET_CLONE_DIR  as shown above.  i.e. $BITBUCKET_CLONE_DIR/<APP_LOCATION>

The  API_TOKEN  value is self-managed and is manually configured. 


 






























Property 

Description 

Example 

Required 

app_location 

Location of your application code. 

Enter / if your application source code is at the root of the repository, or /app if your application code is in a directory called app. 

Yes 

api_location 

Location of your Azure Functions code. 

Enter /api if your app code is in a folder called api. If no Azure Functions app is detected in the folder, the build doesn’t fail, the workflow assumes you don’t want an API. 

No 

output_location 

Location of the build output directory relative to the app_location. 

If your application source code is located at /app, and the build script outputs files to the /app/build folder, then set build as the output_location value. 

No 


  • Select Add variables. 

  • Add a new variable in Deployments section. 

  • Name the variable deployment_token (matching the name in the workflow). 

  • Copy the deployment token that you previously pasted into a text editor. 

  • Paste in the deployment token in the Value box. 


RupaReddy_14-1643804214954.png


 


 



  • Make sure the Secured checkbox is selected. 

  • Select Add. 

  • Select Commit file and return to your pipelines tab. 

  • You can see that the pipeline run is in progress with name Initial Bitbucket Pipelines configuration. 

  • Once the deployment is successful, navigate to the Azure Static Web Apps Overview which includes links to the deployment configuration. Note how the Source link now points to the branch and location of the Bitbucket repository. 

  • Select the URL to see your newly deployed website.


RupaReddy_0-1643804687583.png


 


Clean up resources 


Clean up the resources you deployed by deleting the resource group. 



  • From the Azure portal, select Resource group from the left menu. 

  • Enter the resource group name in the Filter by name field. 

  • Select the resource group name you used in this tutorial. 

  • Select Delete resource group from the top menu. 


Additional resources