Rapid onboarding
“Instant” optimization
Effortless move to new versions
Strong SLAs
Scaling/performance
Cost, Move from CapEx to OpEx
Cross-organization collaboration
Ease storage burden
Hype
- business/ cio - http://avepoint.s3.amazonaws.com/whitepapers/Office365_SharePoint_Online_CIO.pdf?AWSAccessKeyId=AKIAIEDX2UZTNPD3ZZQQ&Expires=1411720803&Signature=%2FVQ1lcwTCJJpRWJZf1K%2FFYVUvHA%3D
Architect - http://avepoint.s3.amazonaws.com/whitepapers/Office365_SharePoint_Online_Architectural_Considerations.pdf?AWSAccessKeyId=AKIAIEDX2UZTNPD3ZZQQ&Expires=1411721194&Signature=ot3J3ET17fyq%2F%2B%2F5L68vaoMgIzw%3D
Elasticity: key proterties
Ability to rapidly ramp up or reduce capacity.
Capacity to deploy servers
Ex: Amazon.com – paying for what you use – during times when you’ll expect peak load – deploy additional VMs to distribute load.
The amazon.com example relates to them basically turning on TONS of additional hardware/computing power over the holidays, to handle the drastically increased traffic over that time.
from an expenditure standpoint – with the cloud, we no longer have to plan for the ‘worst case scenario’ or live with poor performance during peak activity times, we can simply spin up additional resources as necessary.
Realistically – I’m not sure of any organization that can stand up SharePoint, Exchange, and Lync overnight to support their entire user base.
Growth – people OR growth in activity/load that will be placed on your servers -
Economic Pressure
Constantly Onboarding Users
Maintaining User Accounts well after they’ve graduated
Records
Active E-mail Accounts
Alumni Support and Portals
Tight Regulation around Financial Information
Loan Data
Medical and Insurance Records
Academic History, Student Record
Business - http://avepoint.s3.amazonaws.com/whitepapers/Office365_SharePoint_Online_CIO.pdf?AWSAccessKeyId=AKIAIEDX2UZTNPD3ZZQQ&Expires=1411720803&Signature=%2FVQ1lcwTCJJpRWJZf1K%2FFYVUvHA%3D
Security, data sovereignity, SLAs
Architect - http://avepoint.s3.amazonaws.com/whitepapers/Office365_SharePoint_Online_Architectural_Considerations.pdf?AWSAccessKeyId=AKIAIEDX2UZTNPD3ZZQQ&Expires=1411721194&Signature=ot3J3ET17fyq%2F%2B%2F5L68vaoMgIzw%3D
Missing features, authentication, workloads, slas
Integration with internal systems
Ability to customize
Test/staging environment
Data sovereignty
Offline/low bandwidth accessibility
Security and availability concerns persist
Iaas:
Paas:
Saas:
Each offers customers a different level of usability and control
IAAS allows customers to run any applications they please on cloud hardware of their choice. You rent servers
PAAS allows customers to run their own applications and manage their own data. is a cloud model designed for software developers that streamlines the development process by shifting specific aspects of systems management to the service provider. PaaS is used to develop web and mobile applications using components that are pre-configured and maintained by the service provider, including programming languages, application servers and databases.
SAAS allows user to run existing online applications
Focusing on O365. We get SPOL, complexity of SP installation, same for Exchange and Lync. Imagine traditionally the deployment of those solutions, now in a few minutes.
As we’ve shown- there are absolutely other opportunities to leverage the cloud, and gain some of the benefits we discussed earlier in terms of scalability and more –
However, for this presentation, we’re focusing in on Office 365, Microsoft’s SaaS offering and looking at some deployment options specific to that. With so many options that are out there, we could spend many many hour long sessions going over options and opportunities – so in order to remain within our time constraints, I want to focus in on this particular offering, and how we’ve seen customers begin to deploy and utilize this service, making sure you’re aware of the pros and cons of each before reviewing how we’re actually going to GET to the cloud once we’ve made the decision that’s most appropriate for us and what we want to gain out of Microsoft’s productivity stack.
So with that – let’s look at Office 365 deployment options.
The all-in approach will typically come from the Small Business on the Standard service with less than 50 employees. This is the major target market for Microsoft on General Availability and plays into the hands of companies who don’t want to have to support the infrastructure internally in a datacenter or worse…under their desk in the office.
In most cases, this will be an introduction to SharePoint and Lync, and most likely only had an Exchange on-premise instance that they migrate over. The all-in approach, at least for SharePoint Online, might be a good option to consider for organizations currently not using SharePoint on-premises.
PROS: Single Management, Cost-effective means by which to obtain SharePoint, Lync and Exchange (licenses and servers), Fast deployment)
CONTR: Storage limitations, missing features
So instead – what we’ve typically seen as an initial deployment for Office 365 – looks like this: (click)
Untrusted Non-SP Hybrid
The untrusted approaches do not have any authentication link between the on-premise authentication provider and the SharePoint Online Microsoft Online ID provider
Much like the path of BPOS when it was released, the predecessor to Office 365, a general pattern in the industry will see Organizations “testing the water” by outsourcing Lync and Exchange first due to the simplicity of the migration effort and implementation. The reason for this is most organizations do not currently use Lync due to on-premise Infrastructure costs and typically leverage 3rd Party alternatives for Instant Messaging, Voice and Online Meetings.
NOTE: POWER BI NOW AVAILABLE! Once again showcasing MSFT’s commitment to improving cloud offering at a VERY rapid pace. So previously, we might have needed to keep BI workloads on prem, however now we have the option to put those workloads in the cloud as well.
Untrusted Hybrid
Organization may wish to “dip their toe in the water” a little further by allowing certain services to be hosted on SharePoint Online. The most common services here would be Collaboration due to minimal requirements on on-premise functionality missing in SharePoint 2013 on-premise. The major concern here is that in an untrusted SharePoint Online environment, End Users will have to repeatedly authenticate with two different credentials to access the systems.
More examples of usages
Trusted Hybrid
The Trusted Hybrid is similar to the untrusted, but a trusted federation with the Organizations Active Directory ensures End Users require only one set of credentials. With a unified authentication, My Sites can be located either on-premise or in the cloud and each SharePoint Site Collection configured to point to that location.
More complex management -> start looking for 3rd parties.
Extranet
Organizations frequently have the requirement for collaborating outside of the firewall and this presents many barriers to setting this up such as: loosening firewalls, implementing SSL, bandwidth/performance considerations, identifying the source of external user authentication, securing internal content etc.
Realize what you’re getting into if you’re taking the hybrid approach -
Okay, I ve decided. Now what?
Based on information management requirements. We just saw high-level opportunities and pros and cons of each deployment scenario, including hybrid scenarios. I want to spend more time and drill down into how we might arrive at the conclusion that a ‘untrusted, hybrid’ scenario might be best for us, as opposed to an ‘all in’ approach.
CREDIT DAN HOLME – explain that while it’s imporant to distinguish these two from each other as part of information governance strategy- they are very related – as due to how SHarePoint is structured, and where management controls are located (e.g. at site level, site collection level) – if we have info management requirements that differ for content, this may mean we need to [architecturally] create a new container for that content. Which then in turn, will affect how easy it is (or not) to implement controls across your entire environment.
• Information architecture describes content that is part of a solution. Components of information architecture include metadata and content types (“taxonomy”), the site map, and search-related elements. In the examples above, we already see that governance has specified that we must have metadata about the business criticality and the confidentiality of documents. The business must provide the values for that metadata, and the service must account for those classifications.
• Information management requirements define the lifecycle and security of content. Here we see definitions of security and auditing. We also see that collaboration content will have an end-of-life (expiration date).
As we saw previously- different types of content that we manage have different requirements around who gets to access and modify content, and what processes must be in place for content approvals, what SLAs for availability we need to meet – these controls “sit” at different object levels in SharePoint. And at which level those controls can be managed will help drive our information architecture.
This slide emphasizes that information architecture should be planned only after you’ve set requirements for the different types and sets of content you plan to manage. For instance, blocked file types are controlled at the Web App level, as are upload size limitations. So if on my marketing site, I want to be able to upload large videos and files for later viewing, that will either change the setting for all the other sites and site collections in that web app, or I’m going to have to create a new Web app specifically for certain file types and large files, that I would later expose thru web parts or links or other thru my standard portal.
BUT – creating these different containers then complicates our management strategy, resulting in the need for scripting or third party tools to implement control for permissions across sites and site collections, for instance.
Not going to talk about farm-level, or zone, service level as much…
Service:
Active Directory markers
Installation blocker
Registry
Group Policy
Separate farms used for:
Code isolation
Dev / Test / Staging / Production
Access
Public-facing web site
Extranet in Cloud: Partners & Customers
Geoperformance
Collaboration farm(s) with team sites
Feature and process isolation
Enterprise SharePoint farm with intranet and enterprise services
Enterprise services: search, metadata, social (User Profiles, My Sites)
Premium farm(s) for custom applications
Consider the implications
SLAs
Chargebacks
Upgrade to vNext
So what all drives IA? The main thing here, is information management.
On one hand, we have compliance regulations telling us that content must be retained for a certain amount of time, and that we can reduce our organizational risk by restricting access to certain types of secure content. The only secure system is one that is turned off.
And then that has to be balanced with what the business is actually hoping to get out of these solutions- what value we’re looking to deliver. There- you may have requirements for social collaboration for instance, that over-ride the compliance team’s concerns that the wrong information will be posted to the wrong newsfeed.
In the middle – we have to have some way to manage it all – keep some kind of grip on security controls, permissions, to mitigate risk while still providing business solutions.
Compliance – typically this is where a lot of your information management requirements come from for content retention, classification, SLAs (availability), etc.
But also:
HIPAA, FISMA, Gramm–Leach–Bliley Act (GLBA), PIPEDA
Rule of thumb – the more people that will view content on our intranet, for instance – will determine the level of governance controls. For instance, who is allowed to update our company logo on our intranet (portal) homepage should be HIGHLY restricted, whereas maybe I don’t care so much if you want the theme color of your mysite to be purple.
Talk about examples: i.e team site, with specific template, permissions, auditing options, security groups…
Once you determine what cloud deployment option might be most appropriate- you need to get there. Especially with SharePoint –this is where we see the biggest concern – as MSFT no longer offers database shipping or anything like that like they did in the earlier days of BPOS/O365 – so pretty much you’re stuck looking at 3rd party vendors (like us )
Migration a lot of times seems very daunting – but the thing to remember- no matter what you’re moving – is that it can also be an opporutnity for us to re-evaluate the risk levels and health of our current environment, and get things back under control.
We have a lot of customers really wanting to get a handle on governance and compliance from a business perspective, and we have IT departments that want to move to the latest versions of technology for the new features and functionality – so a lot of times for IT to gain business approval (and FUNDING) we will also have to “sell” migration to our businesses as a way for them to get various controls or content structure implemented more easily.
When determining which approach is best for you…
The WHO can help is a big factor in whether to go manual/automated (3rd party) – as if you have extremely limited resources or can’t pull people from other products, the 3rd party / more automated route will be best.
These are typically the things migration customers care about- namely speed, fidelity, and platform coexistence
Installing an agent allows us to utilize additional APIs, and speed up the migration process
Reviewed: Why and when cloud makes sense
Deployment opps
Challenges
What to keep in mind for IA planninghow to get there once we’ve determined what’s best –
For those interested -
The industry’s first and only 100% Microsoft Azure-based Software-as-a-Service (SaaS) platform for Office 365.
Requires no installation.
Requires no agents.
Provides a central home for your business users, decision makers, and IT administrators.
Allows users to seamlessly access resources and extends cloud computing as your needs dictate.
Full services provider for your enterprise cloud platforms.
With simplified Office 365 administration, compliance, and governance, AvePoint
Online Services empower organizations to extend cloud computing as dictated by
specific business needs.
AvePoint Online Services offers tools to manage, protect, govern, and ensure
the compliance of SharePoint Online content using comprehensive configurations.
AvePoint Online Services allow organizations to maintain the same level of
protection and control over their cloud-based assets as with on-premises solutions.