Many "clouds" support SharePoint 2013. And these many “clouds” can be combined adding unique value based on your unique requirements. This session is designed to help ITI's and ITDM's find the right cloud formula to deploy based on practical business and technical considerations. You'll understand how to differentiate between private and public clouds, IaaS and SaaS, as well as hybrid scenarios with absolute clarity of the business benefits and the IT best practices.
14. The NIST-SP 500-291, NIST Cloud Computing Standards
roadmap publication from the National Institute of
Standards
and Technology (NIST) defines cloud computing:
Enabling ubiquitous, convenient, on-demand network access
to a shared pool of configurable computing resources
Rapidly provisioned
Minimal management effort or service provider interaction
18. of workers used an unsanctioned cloud service
for document storage in the last 6 months
41%
87%
$1.8
of these workers knew their company had
policies forbidding such practices
(billion) estimated annual cost to remedy
the data loss
New Mobile Survey Reveals 41% of Employees Are Deliberately Leaking Confidential Data http://onforb.es/18h92Nv
19. • The cloud decision is intrinsically tied to end user
adoption and, ultimately, business alignment
26. Infrastructure
maintained solely
for customer
On premises or off
Managed by the
customer, or by a
3rd party hoster
Private Cloud Hybrid Cloud
Multiple
infrastructure
options
Components both
on premises and
off premises
Management
spread between
customer and 3rd
party hosters
Infrastructure
shared by multiple
customers
Off premises
Managed by 3rd
party on behalf of
customers
Public Cloud
27. Partner Hosted
Private Cloud
• Dedicated environment
• Externally hosted
• Externally or internally
managed
• Internally designed
Self Hosted
Private Cloud
• Dedicated environment
• Internally hosted
• Internally managed
• Internally designed
Shared or Dedicated
Public Cloud
• Shard or dedicated
environment
• Externally hosted
• Externally managed
• Externally designed
Dedicated
Public Cloud
• Partially or fully dedicated
• Externally hosted
• Externally or internally
managed
• Minimal customization
Traditional
on prem
40. • Size and geographical distribution of an organization can affect cloud adoption.
• Regulatory compliance and governance requirements can limit cloud options.
• External collaboration may require on prem farms.
• Service-level agreements (SLAs) may limit cloud options.
• It is important to under the ROI of any proposed solution (and the cost of change).
• Hybrid may be more of a transitional environment from on prem to the cloud.
• Enables customers to use preferred features from SharePoint 2013 on prem and
SharePoint Online.
http://www.sharepointnutsandbolts.com/2014/02/office-365-sharepoint-hybrid-what-you-do-and-do-not-get.html
48. Need space and
maintenance planning Most likely provided
Licensing costs, but
also upgrades and
ongoing support
Included in vendor-
hosted solutions
Need to purchase,
support and maintain,
and upgrade as
platform matures
Included in vendor-
hosted solutions
Administrative,
developer, and end
user skills and training
Still requires
administrative and
possibly dev skills,
end user training
On Premises Cloud Hybrid
Need space and
maintenance planning
Licensing costs, but
also upgrades and
ongoing support
Need to purchase,
support and maintain,
and upgrade as
platform matures
Administrative,
developer, and end
user skills and training
49. Full control
Limited to none in
SaaS, some control
over PaaS, full control
over IaaS
Limited ability to
integrate depending
on SaaS, PaaS, or IaaS
Many limitations OTB,
but very robust tools
from partners
Limited
Very complex across
on prem and cloud
components, very
manual
Needs to be planned,
limited features OTB Defined in SLAs
Some OTB capabilities,
3rd party for tighter
control and
predictability
Microsoft
recommends 3rd
party tools
On Premises Cloud Hybrid
Very complex across
on prem and cloud
components, very
manual
Some OTB capabilities,
3rd party for tighter
control and
predictability
Discuss E2open background, early forays into cloud infrastructure and what we learned about building SaaS offerings. Electronic Data Interchange (EDI)E-commerceTelecom advancesSOAP and XMLService-Oriented ArchitectureWeb ServicesVirtualizationInexpensive hardware
Discuss early days of MMS, and re-learning many of these same issues.
There’s been a lot of talk about the decline in PCs, but in a presentation by Microsoft COO Kevin Turner last summer at a Seattle partner event, Kevin pointed out an important fact: that people may not be buying as many laptops, but they are picking up and using multiple devices on a daily basis. So whether you are supporting PCs and laptops, smartphones, tablets, or embedded devices, realize that your employees and team are using more devices than ever before, and that rate continues to rise.
For Office365 security, Federated Identity Management with Windows Azure ADRecently announced 2-factor authentication supportSupport of your internal ID management policies and procedures for data stored in the cloudHTTPS or data in transitIRM at the document levelInfo Rights ManagemnnetSrvice (RMS) available for encryption at restITAR compliant for physical isolation requirements, as well as HIPAA, FISMA, ISO, and so forthRedundancy, DR and BC, SLAs, with 99.97% global uptime
For all of the reasons mentioned in the intro slides, people want flexibility in their solutions, whether online or offline.
The real risk is not recognizing that your end users are already putting corporate data in the cloud. Use the puppy analogy. Its all about redirect, but in a more secure, controlled way.
You can try it, and if you don’t like it, revert back
Financial decisions about IT are being pushed down to business owners, rather than ITThis is new for many managersMost businesses need something lightweightDesigned for their business, not collaboration overkill
As SharePoint extends into broad adoption and business solutions such as extranets securing the SharePoint content is key.
Customer receives a completed application and functionality with agreed upon SLAs, system uptime, and quality of service (performance). The downside is that there is minimal ability to customize, and new features/updates/changes are driven by market demand or the capabilities of the provider.How do Cloud services differ from traditional managed services?The primary difference is that you say goodbye to the major platform upgrades every 3 or 4 years, and move toward more of an iterative update. As cloud-based service providers, their revenue model changes dramatically as customers move from a high-cost, project-based model to a recurring revenue model.
An environment that provides great application-level control over the SharePoint environment, including access to cloud storage and other services. However, this greater level of application control shifts support/ownership of the application (SharePoint) to the customer.
Delivered as virtual environments and cloud storage. Customer is responsible for the entire platform and applications. Generally used by ISVs, SIs, and customers with very complex, unique development requirements.
Decisions need to be made about build or buy, out source or keep in house
He goes on to say “The emergence of cloud as the core for new 'business as a service' offerings will accelerate cloud adoption and dramatically raise the cloud model's strategic value beyond CIOs to CXOs of all types."
By offering the attributes of public cloud (economics, scale, pace of innovation) with some of the privacy and control features associated with private cloud, VPCs are effectively addressing many of the objections that have held customers back from the cloud model.According to IDC, an important factor driving growth in public IT cloud services spending is the expanding variety of cloud deployment options. As these platforms mature, cloud services adoption will increase dramatically. Virtual private cloud (VPC) offerings are shifting momentum from dedicated private cloud offerings toward public (shared/multi-tenant) cloud offerings.
The level of technical maturity and scope determines what is or can be handled in-house.
SharePoint 2010 also supports single sgn-on (SSO) with Directory Synchronization, and can access resources both on prem and online. However, you cannot share resources cross-farm, which means services like Search will present results side by side and not in a federated manner.SharePoint 2013 uses Oauth, which provides a server-to-server trust relationship, proviing federated search results. Likewise, this would allow BCS (Business Connectivity Services) to access data on prem and within Office365.
As SharePoint extends into broad adoption and business solutions such as extranets securing the SharePoint content is key.
These factors will help you decided how much your own organization can support, as well as help you determine the suitability of vendors