Workspace architecture best practices for Microsoft Sentinel (2022)

  • Article
  • 8 minutes to read

When planning your Microsoft Sentinel workspace deployment, you must also design your Log Analytics workspace architecture. Decisions about the workspace architecture are typically driven by business and technical requirements. This article reviews key decision factors to help you determine the right workspace architecture for your organizations, including:

  • Whether you'll use a single tenant or multiple tenants
  • Any compliance requirements you have for data collection and storage
  • How to control access to Microsoft Sentinel data
  • Cost implications for different scenarios

For more information, see Design your Microsoft Sentinel workspace architecture and Sample workspace designs for common scenarios, and Pre-deployment activities and prerequisites for deploying Microsoft Sentinel.

See our video: Architecting SecOps for Success: Best Practices for Deploying Microsoft Sentinel

Tenancy considerations

While fewer workspaces are simpler to manage, you may have specific needs for multiple tenants and workspaces. For example, many organizations have a cloud environment that contains multiple Azure Active Directory (Azure AD) tenants, resulting from mergers and acquisitions or due to identity separation requirements.

When determining how many tenants and workspaces to use, consider that most Microsoft Sentinel features operate by using a single workspace or Microsoft Sentinel instance, and Microsoft Sentinel ingests all logs housed within the workspace.

Costs are one of the main considerations when determining Microsoft Sentinel architecture. For more information, see Microsoft Sentinel costs and billing.

Working with multiple tenants

If you have multiple tenants, such as if you're a managed security service provider (MSSP), we recommend that you create at least one workspace for each Azure AD tenant to support built-in, service to service data connectors that work only within their own Azure AD tenant.

All connectors based on diagnostics settings cannot be connected to a workspace that is not located in the same tenant where the resource resides. This applies to connectors such as Azure Firewall, Azure Storage, Azure Activity or Azure Active Directory.

Use Azure Lighthouse to help manage multiple Microsoft Sentinel instances in different tenants.


(Video) Microsoft Sentinel Workspace Architecture

Partner data connectors are often based on API or agent collections, and therefore are not attached to a specific Azure AD tenant.

Compliance considerations

After your data is collected, stored, and processed, compliance can become an important design requirement, with a significant impact on your Microsoft Sentinel architecture. Having the ability to validate and prove who has access to what data under all conditions is a critical data sovereignty requirement in many countries and regions, and assessing risks and getting insights in Microsoft Sentinel workflows is a priority for many customers.

In Microsoft Sentinel, data is mostly stored and processed in the same geography or region, with some exceptions, such as when using detection rules that leverage Microsoft's Machine learning. In such cases, data may be copied outside your workspace geography for processing.

For more information, see:

  • Geographical availability and data residency
  • Data residency in Azure
  • Storing and processing EU data in the EU - EU policy blog

To start validating your compliance, assess your data sources, and how and where they send data.


The Log Analytics agent supports TLS 1.2 to ensure data security in transit between the agent and the Log Analytics service, as well as the FIPS 140 standard.

If you are sending data to a geography or region that is different from your Microsoft Sentinel workspace, regardless of whether or not the sending resource resides in Azure, consider using a workspace in the same geography or region.

Region considerations

Use separate Microsoft Sentinel instances for each region. While Microsoft Sentinel can be used in multiple regions, you may have requirements to separate data by team, region, or site, or regulations and controls that make multi-region models impossible or more complex than needed. Using separate instances and workspaces for each region helps to avoid bandwidth / egress costs for moving data across regions.

Consider the following when working with multiple regions:

  • Egress costs generally apply when the Log Analytics or Azure Monitor agent is required to collect logs, such as on virtual machines.

  • Internet egress is also charged, which may not affect you unless you export data outside your Log Analytics workspace. For example, you may incur internet egress charges if you export your Log Analytics data to an on-premises server.

    (Video) Architecting SecOps for Success: Best Practices for Deploying Azure Sentinel Part 1

  • Bandwidth costs vary depending on the source and destination region and collection method. For more information, see:

    • Bandwidth pricing
    • Data transfers charges using Log Analytics .
  • Use templates for your analytics rules, custom queries, workbooks, and other resources to make your deployments more efficient. Deploy the templates instead of manually deploying each resource in each region.

  • Connectors that are based on diagnostics settings do not incur in-bandwidth costs. For more information, see Data transfers charges using Log Analytics.

For example, if you decide to collect logs from Virtual Machines in East US and send them to a Microsoft Sentinel workspace in West US, you'll be charged ingress costs for the data transfer. Since the Log Analytics agent compresses the data in transit, the size charged for the bandwidth may be lower than the size of the logs in Microsoft Sentinel.

If you're collecting Syslog and CEF logs from multiple sources around the world, you may want to set up a Syslog collector in the same region as your Microsoft Sentinel workspace to avoid bandwidth costs, provided that compliance is not a concern.

Understanding whether bandwidth costs justify separate Microsoft Sentinel workspaces depend on the volume of data you need to transfer between regions. Use the Azure Pricing Calculator to estimate your costs.

For more information, see Data residency in Azure.

Access considerations

You may have situations planned where different teams will need access to the same data. For example, your SOC team must have access to all Microsoft Sentinel data, while operations and applications teams will need access to only specific parts. Independent security teams may also need to access Microsoft Sentinel features, but with varying sets of data.

Combine resource-context RBAC and table-level RBAC to provide your teams with a wide range of access options that should support most use cases.

For more information, see Permissions in Microsoft Sentinel.

Resource-context RBAC

The following image shows a simplified version of a workspace architecture where security and operations teams need access to different sets of data, and resource-context RBAC is used to provide the required permissions.

In this image, the Microsoft Sentinel workspace is placed in a separate subscription to better isolate permissions.

(Video) Architecting and Designing Microsoft Sentinel


Another option would be to place Microsoft Sentinel under a separate management group that's dedicated to security, which would ensure that only minimal permission assignments are inherited. Within the security team, several groups are assigned permissions according to their functions. Because these teams have access to the entire workspace, they'll have access to the full Microsoft Sentinel experience, restricted only by the Microsoft Sentinel roles they're assigned. For more information, see Permissions in Microsoft Sentinel.

In addition to the security subscription, a separate subscription is used for the applications teams to host their workloads. The applications teams are granted access to their respective resource groups, where they can manage their resources. This separate subscription and resource-context RBAC allows these teams to view logs generated by any resources they have access to, even when the logs are stored in a workspace where they don't have direct access. The applications teams can access their logs via the Logs area of the Azure portal, to show logs for a specific resource, or via Azure Monitor, to show all of the logs they can access at the same time.

Azure resources have built-in support for resource-context RBAC, but may require additional fine-tuning when working with non-Azure resources. For more information, see Explicitly configure resource-context RBAC.

Table-level RBAC

Table-level RBAC enables you to define specific data types (tables) to be accessible only to a specified set of users.

For example, consider if the organization whose architecture is described in the image above must also grant access to Office 365 logs to an internal audit team. In this case, they might use table-level RBAC to grant the audit team with access to the entire OfficeActivity table, without granting permissions to any other table.

Access considerations with multiple workspaces

If you have different entities, subsidiaries, or geographies within your organization, each with their own security teams that need access to Microsoft Sentinel, use separate workspaces for each entity or subsidiary. Implement the separate workspaces within a single Azure AD tenant, or across multiple tenants using Azure Lighthouse.

Your central SOC team may also use an additional, optional Microsoft Sentinel workspace to manage centralized artifacts such as analytics rules or workbooks.

For more information, see Simplify working with multiple workspaces.

Technical best practices for creating your workspace

Use the following best practice guidance when creating the Log Analytics workspace you'll use for Microsoft Sentinel:

  • When naming your workspace, include Microsoft Sentinel or some other indicator in the name, so that it's easily identified among your other workspaces.

  • Use the same workspace for both Microsoft Sentinel and Microsoft Defender for Cloud, so that all logs collected by Microsoft Defender for Cloud can also be ingested and used by Microsoft Sentinel. The default workspace created by Microsoft Defender for Cloud will not appear as an available workspace for Microsoft Sentinel.

    (Video) Microsoft Sentinel Best Practice for Admin Users

  • Use a dedicated workspace cluster if your projected data ingestion is around or more than 1 TB per day. A dedicated cluster enables you to secure resources for your Microsoft Sentinel data, which enables better query performance for large data sets. Dedicated clusters also provide the option for more encryption and control of your organization's keys.

Don't apply a resource lock to a Log Analytics workspace you'll use for Microsoft Sentinel. A resource lock on a workspace can cause many Microsoft Sentinel operations to fail.

Simplify working with multiple workspaces

If you do need to work with multiple workspaces, simplify your incident management and investigation by condensing and listing all incidents from each Microsoft Sentinel instance in a single location.

To reference data that's held in other Microsoft Sentinel workspaces, such as in cross-workspace workbooks, use cross-workspace queries.

The best time to use cross-workspace queries is when valuable information is stored in a different workspace, subscription or tenant, and can provide value to your current action. For example, the following code shows a sample cross-workspace query:

union Update, workspace("contosoretail-it").Update, workspace("WORKSPACE ID").Update| where TimeGenerated >= ago(1h)| where UpdateState == "Needed"| summarize dcount(Computer) by Classification

For more information, see Extend Microsoft Sentinel across workspaces and tenants.

Next steps

Design your Microsoft Sentinel workspace architecture

Microsoft Sentinel sample workspace designs

On-board Microsoft Sentinel

Get visibility into alerts

(Video) Architecting SecOps for success: Best practices for deploying Azure Sentinel part 2


What is the minimum number of Microsoft Sentinel workspaces that you should create? ›

If you have multiple tenants, such as if you're a managed security service provider (MSSP), we recommend that you create at least one workspace for each Azure AD tenant to support built-in, service to service data connectors that work only within their own Azure AD tenant.

How many workspaces does Azure Sentinel have? ›

Cross-workspace analytics rules

You can include up to 20 workspaces in a single query. You must deploy Microsoft Sentinel on every workspace referenced in the query.

What is Azure Sentinel architecture? ›

Microsoft Azure Sentinel is a scalable, cloud-native security information event management (SIEM) and security orchestration automated response (SOAR) solution. Azure Sentinel delivers intelligent security analytics and threat intelligence across an enterprise.

How do I make Azure Sentinel workspace? ›

Enable Microsoft Sentinel
  1. Sign in to the Azure portal. Make sure that the subscription in which Microsoft Sentinel is created is selected.
  2. Search for and select Microsoft Sentinel.
  3. Select Add.
  4. Select the workspace you want to use or create a new one. ...
  5. Select Add Microsoft Sentinel.
1 Nov 2022

What should you use in Microsoft Sentinel to see? ›

Microsoft Sentinel supports Jupyter notebooks in Azure Machine Learning workspaces, including full libraries for machine learning, visualization, and data analysis. Use notebooks in Microsoft Sentinel to extend the scope of what you can do with Microsoft Sentinel data.

What should you create first in Microsoft Sentinel? ›

We recommend that when you set up your Microsoft Sentinel workspace, create a resource group that's dedicated to Microsoft Sentinel and the resources that Microsoft Sentinel uses, including the Log Analytics workspace, any playbooks, workbooks, and so on.

What is the difference between Microsoft Sentinel and Azure Sentinel? ›

Azure Sentinel, now known as Microsoft Sentinel, centralizes your threat collection, detection, response, and investigation efforts. It provides threat intelligence and intelligent security analytic capabilities that facilitate threat visibility, alert detection, threat response, and proactive hunting.

Is Azure Sentinel a SIEM or soar? ›

Microsoft Sentinel is a cloud-native security information and event manager (SIEM) platform that uses built-in AI to help analyze large volumes of data across an enterprise—fast.

What is a sentinel workspace? ›

Azure Sentinel uses a Log Analytics workspace as its backend, storing events and other information. Log Analytics workspaces are the same technology as Azure Data Explorer uses for its storage. These backends are ultra-scalable, and you can get back results in seconds using the Kusto Query Language (KQL).

Where does Microsoft Sentinel store collected data? ›

Microsoft Sentinel security analytics data is stored in an Azure Monitor Log Analytics workspace. Billing is based on the volume of that data in Microsoft Sentinel and the Azure Monitor Log Analytics workspace storage.

What are the 3 deployment modes that can be used for Azure? ›

There are several ways to deploy cloud resources. Options for deployment in Azure include public, private and hybrid cloud. All three choices provide similar benefits – including cost-effectiveness, performance, reliability and scale.

Is Sentinel a SaaS or PaaS? ›

Sentinel offers a wide variety of cloud-based business applications available as Software as a Service (SaaS) solutions. They are designed to help your organization achieve business goals through innovation.

Is Sentinel a CASB? ›

CASB. Azure Sentinel is a SIEM solution with advanced AI and security analysis capabilities. It integrates with third-party security platforms from vendors such as Fortinet, Symantec and Check Point, as well as Microsoft's Graph Security API.

Which language is used in Azure Sentinel? ›

Microsoft Sentinel uses Azure Monitor's Log Analytics environment and the Kusto Query Language (KQL) to build the queries that undergird much of Sentinel's functionality, from analytics rules to workbooks to hunting.

What is the difference between Azure Sentinel and defender? ›

Microsoft 365 Defender only integrates with other Microsoft cloud products, while Microsoft Sentinel allows you to add third-party (on-premises) products. For example, how can you secure your environment if you can't correlate data from the cloud with your firewall logs? Incident handling.

Can Azure Sentinel work on premise? ›

In fact, Microsoft Sentinel can be successfully used to ingest and correlate data from a wide range of log sources located in a variety of cloud platforms (Azure, AWS, and Google Cloud), on-premises network and compute infrastructure, 3rd party security tools (including firewalls), or software as a service (SaaS) ...

Which rule setting should you configure to meet the Microsoft Sentinel requirements? ›

Which rule setting should you configure to meet the Azure Sentinel requirements? A. From Set rule logic, turn off suppression.

Why would a security analyst benefit from using Microsoft Sentinel notebooks? ›

For example, use notebooks to: Perform analytics that aren't provided out-of-the box in Microsoft Sentinel, such as some Python machine learning features. Create data visualizations that aren't provided out-of-the box in Microsoft Sentinel, such as custom timelines and process trees.

What is playbook in Azure Sentinel? ›

Playbooks in Microsoft Sentinel are based on workflows built in Azure Logic Apps, a cloud service that helps you schedule, automate, and orchestrate tasks and workflows across systems throughout the enterprise.

What are the components of Azure Sentinel? ›

The services that can be connected directly via out-of-the-box integration include Azure Active Directory, Azure Activity, Azure DDoS Protection, Azure AD Identity Protection, Azure Firewall, Azure Security Center, Azure Web Application Firewall, Office 365, Microsoft Defender for Identity, Amazon Web Services - ...

Which users can dismiss incidents in Microsoft Sentinel? ›

Security engineers

Manage incidents, such as assigning or dismissing incidents. Create and edit workbooks, analytics rules, and other Microsoft Sentinel resources.

Is Sentinel better than Splunk? ›

Microsoft Sentinel is generally rated as being easier to use, set up, and administrate. Splunk generally gets better ratings for quality of support and ease of doing business. Most people trust Microsoft's products more, including its Network Management, Incident Management, and Security Intelligence.

Is Microsoft Sentinel an XDR? ›

Microsoft Sentinel is a cloud-native SIEM tool; Microsoft 365 Defender provides XDR capabilities for end-user environments (email, documents, identity, apps, and endpoint); and Microsoft Defender for Cloud provides XDR capabilities for infrastructure and multi-cloud platforms including virtual machines, databases, ...

Is Azure Sentinel an XDR? ›

To reiterate, Microsoft Defender provides XDR capabilities for end-user environments. On the other hand, Sentinel provides XDR capabilities for infrastructure and cloud platforms.

Why SOAR is better than SIEM? ›

While SIEM ingests various log and event data from traditional infrastructure component sources, a SOAR pulls in information from external emerging threat intelligence feeds, endpoint security software and other third-party sources to get a better overall picture of the security landscape inside the network and out.

Is Azure Sentinel a SOC? ›

Microsoft Azure Sentinel Security Operations Centre (SOC) and Managed Detection and Response (MDR) Quorum Cyber's fully-managed Security Operations Centre (C-SOC) and Managed Detect and Response (MDR) service, providing a cloud-native, 24x7 cyber risk mitigation platform, built and operated in the UK.

What database does Azure Sentinel use? ›

Azure Sentinel uses Azure Monitor which is built on a proven and scalable log analytics database that ingests more than 10 petabytes every day and provides a very fast query engine that can sort through millions of records in seconds.

What is Log Analytics workspace for Sentinel? ›

A Log Analytics workspace is a unique environment for log data from Azure Monitor and other Azure services, such as Microsoft Sentinel and Microsoft Defender for Cloud. Each workspace has its own data repository and configuration but might combine data from multiple services.

What is AML workspace? ›

The workspace is the top-level resource for Azure Machine Learning, providing a centralized place to work with all the artifacts you create when you use Azure Machine Learning. The workspace keeps a history of all training runs, including logs, metrics, output, and a snapshot of your scripts.

What are the benefits of Azure Sentinel? ›

Microsoft Sentinel benefit for Microsoft 365 E5, A5, F5, and G5 customers
  • Comprehensive security. Get end-to-end visibility across your resources, including users, devices, applications, and infrastructure.
  • Detect advanced threats. ...
  • Investigate prioritized incidents. ...
  • Enable efficient and effective response.

What is the maximum data retention period of a Microsoft Sentinel workspace? ›

Out of the box, Microsoft Sentinel provides 90 days of data retention for free. In some parts of the world and within certain industries, there are regulations that organizations must adhere to which require data retention up to 7 years or longer.

How long does Azure Sentinel store logs? ›

By default, a Log Analytics workspace has a retention period of 30 days. Retention is calculated on the ingestion date for data, so if a workspace uses the default retention period, it means that Azure removes data from the workspace 30 days after its ingestion.

Is Microsoft Sentinel part of E5? ›

This is included within Microsoft 365 E5 and also included within the E5 Security add-on (alongside Azure AD Plan 2).

What are the 4 cloud deployment types? ›

NIST defines four cloud deployment models: public clouds, private clouds, community clouds, and hybrid clouds. A cloud deployment model is defined according to where the infrastructure for the deployment resides and who has control over that infrastructure.

Which is the best deployment model and why? ›

Public Cloud

Public deployment models in the cloud are perfect for organizations with growing and fluctuating demands. It also makes a great choice for companies with low-security concerns. Thus, you pay a cloud service provider for networking services, compute virtualization & storage available on the public internet.

What are the 3 main steps in the deployment process? ›

Software deployment process mainly consists of 3 stages: development, testing and monitoring.

Does Sentinel have an API? ›

Microsoft Sentinel REST APIs allow you to create and manage data connectors, analytic rules, incidents, bookmarks, and get entity information.

Is Azure Sentinel a MDR? ›

Microsoft Azure Sentinel enables Open Systems to provide a compelling cloud-native MDR service that helps give enterprises all the advantages of a 'SOC',” said Ann Johnson, CVP Cybersecurity Solutions Group, Microsoft.

What are the 4 pillars of CASB? ›

The Four Pillars of CASB: Visibility
  • Activity Logs. When it comes to sensitive data, an organization must have full visibility and knowledge over how it is being used. ...
  • Shadow IT. ...
  • CSPM.

Does CASB replace VPN? ›

CASB offers the visibility across the computing environment that VPNs just can't provide, which helps IT security better understand application usage and gain better control over network assets. Though CASB is a powerful security tool, it isn't sufficient for every situation.

What is the difference between CASB and SIEM? ›

SIEM mainly deals with the internal part of the operations. CASB i.e. Cloud Access Security Broker, on the other hand, is a system that covers it for the cloud region, and we can say that CASB is a kind of blanket over any existing SIEM system.

What is EPS in Azure Sentinel? ›

I have been tasked to determine the estimate of EPS (events per second) for 4 subscriptions.

Can Azure Sentinel remediate incidents automatically? ›

Playbooks in the Sentinel offers automated remediation and proactive action tools to handle many incidents on autopilot. The playbook uses the Azure Logic App designer to build the workflow for automated response actions.

Where does Azure Sentinel store collected data? ›

Microsoft Sentinel security analytics data is stored in an Azure Monitor Log Analytics workspace. Billing is based on the volume of that data in Microsoft Sentinel and the Azure Monitor Log Analytics workspace storage.

What should you use in Microsoft Sentinel to see the visualization? ›

Once you have connected your data sources to Microsoft Sentinel, you can visualize and monitor the data using the Microsoft Sentinel adoption of Azure Monitor Workbooks, which provides versatility in creating custom dashboards.

What is the best way to visualize data? ›

The two most common formats for visualizing data are dashboards and reports. This allows you to showcase several different images to paint a more compelling story. In fact, the average dashboard, according to our experts, contains 3-5 charts or graphs.

What are the four security operation areas of Microsoft Sentinel that cover this area? ›

What are the four security operation areas of Azure Sentinel that cover this area? Collect, Detect, Investigate, and Respond. Your estate has many different data sources where data is stored.

What are analytic rules in Sentinel? ›

Analytics rules search for specific events or sets of events across your environment, alert you when certain event thresholds or conditions are reached, generate incidents for your SOC to triage and investigate, and respond to threats with automated tracking and remediation processes.

What problems is Microsoft Sentinel solving and how is that benefiting you? ›

Microsoft Sentinel delivers intelligent security analytics and threat intelligence across the enterprise. With Microsoft Sentinel, you get a single solution for attack detection, threat visibility, proactive hunting, and threat response.

How many minimum data centers are there in Azure availability groups? ›

To ensure resiliency, a minimum of three separate availability zones are present in all availability zone-enabled regions.

What is the minimum number of app service plans that should be created in Azure? ›

The minimum number of app service plans that should be created is 4. The web apps use different runtime stacks, so they will each require their own app service plan.

What is the minimum number of instances necessary to get the SLD guarantee from Microsoft? ›

Answer. For all Virtual Machines that have two or more instances deployed in the same Availability Set, we guarantee you will have Virtual Machine Connectivity to at least one instance, at least 99.95% of the time.

What is the minimum number of nodes required for Azure VMware solution? ›

A minimum of three nodes are required to deploy Azure VMware Solutions Private Cloud.

What is the difference between availability zone and data center? ›

An availability zone is a logical data center in a region available for use by any AWS customer. Each zone in a region has redundant and separate power, networking and connectivity to reduce the likelihood of two zones failing simultaneously. A common misconception is that a single zone equals a single data center.

Do all Azure regions have 3 availability zones? ›

Each Azure region has a minimum of three availability zones, allowing you to run two isolated copies of your applications.

What is the distance between 2 availability Zones Azure? ›

Azure Availability Zones

Each region is separated by at least 300 miles (typically) to reduce the likelihood that a natural disaster in one region affects the other region.

What is difference between app service and app service plan? ›

An App Service Environment is a single-tenant deployment of Azure App Service that runs on your virtual network. Applications are hosted in App Service plans, which are created in an App Service Environment. An App Service plan is essentially a provisioning profile for an application host.

What are the three kinds of app service in Azure? ›

App Services
  • Web App – used for hosting websites and web applications (previously Azure Websites)
  • API App – used for hosting the RESTful APIs.
  • Logic App – used for business process automation, system integration and sharing data across clouds.
6 Mar 2017

What is the minimum number of VMs required for an availability set? ›

Availability sets

We recommended that two or more VMs are created within an availability set to provide for a highly available application and to meet the 99.95% Azure SLA. There is no cost for the Availability Set itself, you only pay for each VM instance that you create.

What happens if Azure does not meet its own SLA? ›

SLAs For Azure Products And Services

If a service fails to meet the guarantees, a percentage of the monthly service fees can be credited to you.

What is the longest term for a reserved VM instance? ›

An Azure Reserved Virtual Machine Instance (RI) is a virtual machine (VM) on the Microsoft Azure public cloud that has been reserved for dedicated use on a one- or three-year basis.

What is the smallest VM in Azure? ›

You can use windows vms labeled as smalldisk , those will have 30gb os disk size. any linux vm will have 30gb os disk by default.

What is the maximum supported number of VCPU per VM? ›

A VM can use up to 48 vCPUs under VMware's standard ESX host license and the Enterprise edition.

How many cores does a VCPU Azure have? ›

Supports up to 64 vCPUs (32 cores with hyper-threading) and 256 GiB RAM.


1. Learn Live - Configure your Microsoft Sentinel environment
(Microsoft Developer)
2. Microsoft Sentinel - Architecture
(Andre Camillo)
3. Azure Landing Zones | Architectural Blueprint, Tooling & Best Practices
(Microsoft Mechanics)
4. Azure Sentinel webinar: Multi-tenant investigations
(Microsoft Security Community)
5. Get Started with Azure Sentinel
(Andy Malone MVP)
6. Microsoft Sentinel Bootcamp (8 Labs & 29 Exercises)
(Susanth Sutheesh)

Top Articles

You might also like

Latest Posts

Article information

Author: Carmelo Roob

Last Updated: 11/05/2022

Views: 6069

Rating: 4.4 / 5 (45 voted)

Reviews: 92% of readers found this page helpful

Author information

Name: Carmelo Roob

Birthday: 1995-01-09

Address: Apt. 915 481 Sipes Cliff, New Gonzalobury, CO 80176

Phone: +6773780339780

Job: Sales Executive

Hobby: Gaming, Jogging, Rugby, Video gaming, Handball, Ice skating, Web surfing

Introduction: My name is Carmelo Roob, I am a modern, handsome, delightful, comfortable, attractive, vast, good person who loves writing and wants to share my knowledge and understanding with you.