Hello and welcome to this Microsoft 365 Fundamentals Video. My name is Chris Tomiko, and we're gonna be talking about cloud deployment models. This is the last lesson in the last module off the Siri's. So I hope you'll join me all the way through. If you have joined me all the way through.
Thank you so much for sticking with me. I know it's a lot of information.
I've tried to keep it as light and breezy as I could, but obviously we're here to learn. So let's get cracking. All right, So the learning objectives for this lesson. So we're gonna be learning about the considerations to keep in mind when choosing a service, we're gonna be looking at the terminology associated with adopting a cloud service.
We're gonna be looking at the difference between cloud only and hybrid models because that's a key feature.
A swell as when you might want to move to the cloud from legacy software. Okay, because there are There are factors involved that many people don't think about until it's very often too late. Okay, let's get cracking. So let's start with cloud only. So this is generally the service you want to use
when you have no connection to existing on premises systems.
It's strictly in the in the cloud, as it says there on the screen,
on your effectively. It's really, really good for new businesses who don't have a lot of infrastructure when it comes to things like your operational expenditure vs your capital expenditure.
Not many small businesses have a lot of capital, so you want to put things operationally where you pay on a monthly basis or rolling basis. So that's where this comes into play, all right,
so why? So this is good when you as I mentioned, when you don't have any physical infrastructure, it's really easy to set up. Okay. That's why new businesses get involved with them.
So let's discuss, why not? Well,
there's there's one major one you can't customise anything like basically, Microsoft go. This is our system. If you like it, pay us money if you don't go and make your own, and that's effectively what it comes down to. Microsoft have to try and standardise things, because otherwise can you imagine them customizing
For every single customer that comes on board,
it would be a nightmare. I don't think they'd get anything done, but yeah, if you need to be able to customize, then you should look at either a hybrid or an on site option. So cloud is not always the solution, although in many cases usually is.
Let's have a look at hybrid, then in that case, so this is a good one. It's a combination basically of cloud with on premises to support your i t. This is a good one when you already heavily invested in infrastructure, custom applications and things like that.
And it's what you do when you want to merge the two together. This is probably one of the most popular setups I've seen
certainly in my career so far.
So you take your online cloud environment so marks off. 365
You bring your own premises. So we're gonna run my company can toes. Oh,
We're gonna merge them together into a hybrid to the hybrid. We will still be can't Ozo dot com
But what we will have now is instead of having just this physical section here,
you will have a connection
Look at my cloud. Isn't it lovely
on your new organizational section instead of just being here before. Now you're out here
on this section here, creates the new boundary of your network, so to speak, all right.
It allows you to keep critical. Resource is on premises or a line through it allows you to keep critical. Resource is on premises while working with cloud services. And that's probably the key thing with this. Andi, The cloud, effectively, as I mentioned, becomes an extension off your network. That's that's the key thing with hybrid clouds.
You don't have to give up what you already
own and what you already use, so it's easier to move to it.
So the question now is which model, I guess. Well, it comes down to a few things. The first is cost. So you know that Can you afford to move into the cloud? You know, how big is your network? How many licenses are you gonna have to use? Do you have you could look at it the other way as well.
If you're looking for a hybrid environment, do you have the money that you need to update your servers?
For example, is the secure a bit security, secure ability, security and reliability on compliance of the network. Is it going to do what you needed to do? And also is it functional? Like if you have to spend ages learning new stuff?
Andi, then teaching your stuff is with your staff as well.
Then maybe it's not functional, and it doesn't do what you want it to do. Maybe it will just be more hassle than it's worth.
Also, if you've made a recent investment into hardware physically on site, moving to a cloud only model doesn't make sense because you've just spent several £1000 dollars. Whatever money currency you have on brand new servers, you don't just want to throw those out. But then you might also look at the flip side of that and say that if you have outdated hardware and systems,
actually, now might be a good time to move into the cloud because then you don't need to invest in, you know, six brand new servers or whatever it might be that you're looking at.
It's also good if you have limited in house. I t Resource is, if you can't physically look after all those servers and look after the updating of those because you're a one man band or two man band in your department, then maybe a cloud environment is better, because you're effectively paying for Microsoft to do that physical infrastructure for you,
and you just sit on the services attendant
on the final one is available capital. You know, maybe people don't have 2030 £40,000 or dollars to start up a new business,
which, you know it can be that kind of price if you're looking at a lot of service to do work for you, in which case go into azure,
use Microsoft 365 to do your work much, much easier. And very, very eat very much more easier toe balance on the books as an operational expenditure rather than a huge capital expenditure.
All right, so let's look at migration versus co existence here. So, Mr Migration First,
this is way you move everything from an old system to a new one, and it's with the intent of actually moving, removing the old system in in the end result. So a migration means that you move from one location to another. That's what the word is defined as effectively,
whereas co existence is two different systems which could be on premises and in the cloud, and they connect and work together at the same time. Hence co existence and they become a single service. That's that's the key thing here. It's not co existence if you run a cloud environment on an on site, but they're not linked.
That's not co existence.
Coexistence is when the two things cooperate together as a single, as if they were basically one thing. All right,
so here's a lovely little table that I have drawn that explains this so things that you might need to migrate and the strategies and considerations that go with them. So for office 2013 or older, and you want to move up to the new marks or 365 APs
you after April 2023. So this one here, accessing office 365 services won't be supported if you're using office 2013.
Okay, so keep that in mind if you are looking to move off of 2013 in the near future, or certainly if you know you haven't thought about it on office. 2010 is already only supported until 2020. So this year on Office 2007 isn't even supported It also keep those in mind. If you're not in 2013 or higher,
you should consider moving,
basically, is what they're saying.
Office server versions to equivalent office 365 services. So Office Server 2013 and Office Server 2016 products don't take advantage of the cloud based services and enhancements, so they don't use things like the online one. Dr. SharePoint, That kind of thing.
You would need to run those physically. They don't have the
threat protection built into them those kinds of things. So there's more to the cloud environment than just the products that you use if you see what I mean
on a swells. Somewhat, fish Server 2010 products have a specified end of support date, so it's going to run out effectively, whereas if you're in the cloud, you're was on the latest versions effectively
on DSO over 20,007 for this there No, no even supported anymore. But you can actually hire a Microsoft partner to help you with them and then roll out the new stuff to your users Andi, hopefully get rid of that. This is the 2007 office server that you've got running
on Windows seven and Windows 8.1 on your devices. If you want to upgrade them to Windows 10. Enterprise, you basically this one's really easy. We've discussed this in the modern desktops section. You just do an in place upgrade to Windows 10 Enterprise. It's really simple. You literally just tell it to run the upgrade on Walk Away pretty much.
You can even do it so that it is a zero
interface, so you can pre configure it on, say, Windows. Autopilot kicked them off on. Then that's it. You're done. You could just walk away when they've rebooted people. Just logging is normal. All their applications, their files, everything is all in position there. Customization zones, all their absolutely no issue whatsoever.
All right, let me move that one out the way on. We will finish up now with our usual pop quiz. So
knows what has stands for we've been talking about
as a service? I'll give you that, so it's as a service. So the if you've got P
as a service. What does the P stand for? Let's change it slightly. What do you think it might be? So he talked about OS as a service w as a service software as a service.
What do you think he might be? A.
If you said platform, you would be 100% correct. And basically, as I mentioned, the as a service model is used for almost everything. Now, from infrastructure to software, even the operating system. So Windows as a service. I mentioned it in the modern desktops module that we discussed.
So yeah, this is basically what we're looking at when it comes to Microsoft 365 now everything
And that's how it's gonna be whether or not people take it, that remains to be seen. We'll see.
But yeah, that's pretty much it. So let's summarize what we've discussed in this lesson. So we discussed the considerations to keep in mind when choosing a service. So this was the whole crowd only
Onda. We then looked at, for example, capital expenditure, which is cap ex
operational expenditure, which is ah pecks pecks is a lot easier to use when you're starting up a new business cap Ex is probably for slightly bigger businesses. Maybe if they know they've got a budget for the year or for their server maintenance or whatever else.
We also looked at the terminology associated with adopting a cloud service. Eso just talking about the whole as a service environment on Do you know the wording that comes with it with a lot of the basic parts off the cloud environment
and also the difference between cloud only and hybrid models and why you might want to lean towards one and the other
Onda we discussed when you might want to move to the cloud from legacy software, you know, do that migration rather than a co existence. So I put that down there as well. We've got migration, which is actually moving across, and then we had co existence.
And remember, coexistence is only coexistence.
When the two systems work together was one service. If you have two separate systems that you need to administer separately, then that's not coexistence. You're just running to networks. All right, let's wrap up this video here. We're going to go into the next video. I'm gonna run through basically everything we've done in this entire training course.
So we've actually finished all of the content.
All we're gonna do is just quickly recap everything we've done on. Then that will be it. We are done. I will see you in the next video.