In these slides i try to give basics of the Azure Cloud environment and Cloud computing as in general

1. AGENDA
WHY CLOUD?
WHAT IS CLOUD
TYPES OF CLOUD
CLOUD DEPLOYMENT MODEL
TYPES OF CLOUD SERVICE
EXPLORING THE AZURE CLOUD ENVIRONMENT

2. WHY CLOUD?!
BUYING A HOUSE?
• Buy (On-premises), you might invest a significant sum upfront.
• Benefits- Security, a place for you away from the public, you can configure and
run it how you want.

3. RENTING A HOUSE
• Rent(Cloud), you might rent a house, rent a room or stay in a hotel.
• Benefits- Something wrong? House/Room-it's the landlords (cloud providers)
job to fix. Hotel-Hotel takes care of just about everything including your linen.

4. WHAT IS CLOUD
• Delivery of computing services—servers, storage, databases, networking,
software, analytics, intelligence and more—over the internet, enabling faster
innovation, flexible resources, and economies of scale.
• The company providing these services is referred to as a cloud provider.
Example providers are Microsoft Azure, Amazon Web Services (AWS), and the
Google Cloud Platform (GCP).

5. CLOUD
COMPUTING
SERVICES
• Every business has different needs and requirements, and
cloud computing is flexible and cost-efficient. The goal of
cloud computing is to make running a business easier and
more efficient, whether it's a small start-up or a large
enterprise.
• The two most common services that all cloud providers offer
– compute power and storage.

6. ECONOMIES OF SCALE
Ability to do things more efficiently or at a lower-cost per unit when operating at a
larger scale.
Benefits
• Reduce costs and gain efficiency
• Pass those benefits on to their customers
But…do we have limits to the benefits?
• Competition
• Core cost

7. COMPARE CAPEX VS OPEX
• Organisations used to buy new datacenters or new servers to allow them build
out new services, which they could then deliver to their customers. That is no
longer the case.
• Just sign up for a service from a cloud provider to get up and running

8. ..COMPARE CAPEX VS OPEX
Two Approaches to Investments
• Capital Expenditure (CapEx)
• Storage
• Server costs
• Storage costs
• Network costs
• Backup and archive costs
• Organization continuity and disaster recovery costs
• Datacenter infrastructure costs
• Technical personnel
• Operational Expenditure (OpEx):
• Leasing software and customized features
• Scaling charges based on usage/demand instead of fixed hardware or capacity.
• Billing at the user or organization level.

9. CLOUD DEPLOYMENT MODELS
Defines where your data is stored and how your customers interact with it
• Public-Owned by the cloud services provider (also known as a hosting
provider). It provides resources and services to multiple organizations and
users, who connect to the cloud service via a secure network connection.
• Ownership-Resources do not belong to the organization that is utilizing them
• Multiple end users -resources available to multiple organizations.
• Connectivity-over the internet using a web browser.
• Skills-do not require deep technical knowledge

10. …CLOUD DEPLOYMENT MODELS
• Private-Organisations create a cloud environment in their own datacenter and
provide self-service access to compute resources to users within their organization.
• OwnershipThe owner and user of the cloud services are the same.
• Hardware-owner is entirely responsible for the purchase, maintenance, and management of
the cloud hardware
• Users-operates only within one organization and cloud computing resources are used
exclusively by a single business or organization.
• Connectivity-private network that is highly secure./ Does not provide access to the public.
• Skills-deep technical knowledge to set up, manage, and maintain

11. …CLOUD DEPLOYMENT MODELS
• Hybrid-Combines both public and private clouds, allowing you to run your
applications in the most appropriate location
• Resource location. run or are used in a public cloud, and others run or are used in a private
cloud.
• Cost and efficiency-leverage some of the benefits of cost, efficiency, and scale that are
available with a public cloud model.
• Control- retain management control in private clouds.
• Skills-still required to maintain the private cloud and ensure both cloud models can operate
together.

12. TYPES OF CLOUD SERVICE
• Infrastructure as a Service(IAAS)- The most basic, you rent IT infrastructure servers
and virtual machines (VMs), storage, networks, and operating systems from a cloud
provider on a pay-as-you-go basis.
• Upfront costs. IaaS has no upfront costs. Users pay only for what they consume.
• User ownership. The user is responsible for the purchase, installation, configuration, and
management of their own software operating systems, middleware, and applications.
• Cloud provider ownership. The cloud provider is responsible for ensuring that the underlying
cloud infrastructure (such as virtual machines, storage and networking) is available for the user.

13. …TYPES OF CLOUD SERVICE
• Platform as a Service (PaaS) provides an environment for building, testing, and deploying
software applications. The goal of PaaS is to help create an application as quickly as
possible without having to worry about managing the underlying infrastructure.
• Upfront costs. There are no upfront costs, and users pay only for what they consume.
• User ownership. The user is responsible for the development of their own applications. However, they
are not responsible for managing the server or infrastructure. This allows the user to focus on the
application or workload they want to run.
• Cloud provider ownership. The cloud provider is responsible for operating system management, and
network and service configuration. Cloud providers are typically responsible for everything apart from
the application that a user wants to run. They provide a complete managed platform on which to run
an application.

14. …TYPES OF CLOUD SERVICE
• Software as a Service (SaaS) is software that is centrally hosted and managed
for the end customer. It allows users to connect to and use cloud-based apps
over the internet.
• Upfront costs. Users have no upfront costs; they pay a subscription, typically on a
monthly or annual basis.
• User ownership. Users just use the application software; they are not responsible for
any maintenance or management of that software.
• Cloud provider ownership. The cloud provider is responsible for the provision,
management, and maintenance of the application software.

15. …TYPES OF CLOUD SERVICE
• Summary

16. SO WHERE DOES AZURE FIT IN?
• Cloud provider from one of the worlds most reliable
Software provider Microsoft
• Azure provides over 100 services that enable you to
do everything from running your existing applications
on virtual machines to exploring new software
paradigms such as intelligent bots and mixed reality.

17. WHY AZURE?

18. LET’S TAKE A TOUR OF AZURE SERVICES

19. AZURE ARCHITECTURE AND SERVICE
GUARANTEES
• Datacenters-Azure is made up of datacenters located around the globe. The
specific datacenters aren't exposed to end users directly; instead, Azure organizes them
into regions.
• Region-geographical area on the planet containing at least one, but potentially multiple
datacenters that are nearby and networked together with a low-latency network. Azure
intelligently assigns and controls the resources within each region to ensure workloads are
appropriately balanced.
• This gives you the flexibility to bring applications closer to your users no matter where they
are. It also provides better scalability, redundancy, and preserves data residency for your
services.

20. AZURE REGIONS- 54

21. …AZURE ARCHITECTURE AND SERVICE
GUARANTEES
• Azure geography is a discrete market typically containing two or more regions that preserve data residency
and compliance boundaries.
• Geographies ensure that data residency, sovereignty, compliance, and resiliency requirements are honored
within geographical boundaries. customers with specific data residency and compliance needs to keep their
data and applications close.
• Geographies are broken up into the following areas:
• Americas
• Europe
• Asia Pacific
• Middle East and Africa
• Each region belongs to a single geography and has specific service availability, compliance, and data
residency/sovereignty rules applied to it.

22. …AZURE ARCHITECTURE AND SERVICE
GUARANTEES
• Availability Zones are physically separate datacenters within an Azure
region.
• Each Availability Zone is made up of one or more datacenters equipped
with independent power, cooling, and networking. It is set up to be
an isolation boundary

23. …AZURE ARCHITECTURE AND SERVICE
GUARANTEES
• Azure geography is a discrete market typically containing two or more regions that preserve data residency
and compliance boundaries.
• Geographies ensure that data residency, sovereignty, compliance, and resiliency requirements are honored
within geographical boundaries. customers with specific data residency and compliance needs to keep their
data and applications close.
• Geographies are broken up into the following areas:
• Americas
• Europe
• Asia Pacific
• Middle East and Africa
• Each region belongs to a single geography and has specific service availability, compliance, and data
residency/sovereignty rules applied to it.

24. NAVIGATING THE AZURE PORTAL
• The Azure portal is a public website that you can access with any web browser.
Once you sign in with your Azure account, you can create, manage, and
monitor any available Azure services. You can identify a service you're looking
for, get links for help on a topic, and deploy, manage, and delete resources. It
also guides you through complex administrative tasks using wizards and
tooltips.
• Access the same on the internet using the public url
portal.azure.com

25. AZURE SERVICES ACCOUNT STRUCTURE
• Tenant ID- ID of the AAD directory in which you created the application.
• Subscription ID- A subscription is an agreement with Microsoft to use one or
more Microsoft cloud platforms or services, for which charges accrue based on
either a per-user license fee or on cloud-based resource consumption.
• Resource Groups-approach to group a collection of assets in logical groups for
easy or even automatic provisioning, monitoring, and access control, and for
more effective management of their costs.

26. …AZURE SERVICES ACCOUNT STRUCTURE

27. AZURE NETWORKING
• A virtual network is a logically isolated network on Azure. A virtual network allows
Azure resources to securely communicate with each other, the internet, and on-
premises networks. A virtual network is scoped to a single region; however, multiple
virtual networks from different regions can be connected together using virtual
network peering.
• Virtual networks can be segmented into one or more subnets. Subnets help you
organize and secure your resources in discrete sections.
• A network security group, or NSG, allows or denies inbound network traffic to your
Azure resources. Think of a network security group as a cloud-level firewall for your
network.

28. SCALE WITH AZURE LOAD BALANCER
• You now have your site up and running on Azure. But how can you help ensure
your site is running 24/7?
• Say you start by adding additional VMs, each configured identically, to each tier. The
idea is to have additional systems ready, in case one goes down, or is serving too
many users at the same time. The answer is to use a load balancer to distribute
traffic. The load balancer becomes the entry point to the user. The user doesn't
know (or need to know) which system the load balancer chooses to receive the
request.

29. AZURE SECURITY A SHARED RESPONSIBILITY
• Security of the operational environment is now a concern shared by both cloud providers and customers. By shifting
these responsibilities to a cloud service like Azure, organizations can reduce focus on activities that aren't core business
competencies. Depending on the specific technology choices, some security protections will be built into the particular
service, while addressing others will remain the customer's responsibility.
• For all cloud deployment types, you own your data and identities. You are responsible for helping secure your data and
identities, your on-premises resources, and the cloud components you control (which vary by service type).
• Regardless of the deployment type, you always retain responsibility for the following items:
• Data
• Endpoints
• Accounts
• Access management

30. PROTECTING YOUR NETWORK
• Azure follows a layered approach providing multiple levels of protection, so that if an attacker gets through
one layer, there are further protections in place to limit further attack.
• To provide inbound protection at the perimeter, you have several choices.
• Azure Firewall a fully stateful firewall as a service with built-in high availability and unrestricted cloud
scalability. Azure Firewall provides inbound protection for non-HTTP/S protocols
• Azure Application Gateway is a load balancer that includes a Web Application Firewall (WAF) that provides
protection from common, known vulnerabilities in websites.
• Network virtual appliances (NVAs) are ideal options for non-HTTP services or advanced configurations, and
are similar to hardware firewall appliances.

31. …PROTECTING YOUR NETWORK
• DDoS Protection leverages the scale and elasticity of Microsoft's global network to bring DDoS mitigation
capacity to every Azure region. The Azure DDoS Protection service protects your Azure applications by
monitoring traffic at the Azure network edge before it can impact your service's availability. Within a few
minutes of attack detection, you are notified using Azure Monitor metrics
• Virtual network security once inside a virtual network (VNet), it's crucial that you limit communication
between resources to only what is required. For communication between virtual machines, Network Security
Groups (NSGs) are a critical piece to restrict unnecessary communication. Network Security Groups allow you
to filter network traffic to and from Azure resources in an Azure virtual network. An NSG can contain multiple
inbound and outbound security rules that enable you to filter traffic to and from resources by source and
destination IP address, port, and protocol.
• Virtual private network (VPN) connections are a common way of establishing secure communication
channels between networks. Connections between Azure Virtual Network and an on-premises VPN device
are a great way to provide secure communication between your network and your VNet on Azure.

32. THANK YOU BEST
WISHES