I am not a Microsoft Office 365 administrator but I think it's not complex. I think that for certain companies, it may be a little bit complex or difficult for them to understand what the Office 365 package contains.

It is based on the licensing perspective. You can have an E3 license where you have both components and then you can have an E5 license and then you have additional components there. But in some cases, I think it should be more.

I think for the administrators, it will be good for them to have visibility to say, what will be the cost to have Power apps? Or, what will be the cost to have just only Power BI? Or, what is the cost of the full breakdown of all the components? What do the components offer you and give you?

If you are not an IT person and looking at opening your own company and you want to set up some components or Microsoft, you want to make sure that you have all the suites that you need to drive your business. From the perspective of someone that is not an IT person, I think will be useful to have some documentation that could help them in good guidance to, make the best selection and the best choices, because that they will have a better understanding. They would know things like Power Automate would help them to create their own process flow and have their own reports. They would know that they don't need to buy separate applications. It is possible to have everything in one package but sometimes, it's the lack of visibility or lack of communication that prevents this.

On the topic of on-premises versus cloud deployment, we have both because it's not only about a global company. We also have regional countries. On a global aspect, it's on the cloud, whereas on the regional aspect, it's on-premises. In these cases, they are still planning to move to the cloud.

When you look at Office 365, it's on the cloud, fully and independently of the country. However, there are other components that are not Microsoft and those that are on-premises, we are planning to also move to Azure.

The initial setup was very, very easy. It was not complex at all. 

Our original deployment took about six months. We needed about three people to handle it.

As far as I remember, the initial setup was not complicated. It took perhaps a week to set up and we had a team working on it. 

The initial setup isn't complex. The time it takes to deploy depends on the company. While cloud deployment is simpler, on-premises deployment is very different. You'll have a lot of work to do in that case, so it will take longer. 

We use the cloud version of SharePoint, which is pretty much out of the box with Office 365, so we had nothing to install. It was already ready to run and we only had to customize the look and feel. That's it. However, we have done an installation as part of a project for a customer where they had an on-premise SharePoint server.

It is usually a multi-tier environment where you have more than one computer or server for different parts. You have an application server, a database server, and a web front end.
You install the Windows Server, databases, and SQL Server. There are a lot of pieces. With on-premises deployments, there is a lot more hardware, and you have to worry about everything. In cloud deployments, you don't have that responsibility. Security is taken care of in cloud deployments.

Deployment duration depends on the number of users and the size of your implementation. It could take a year or so for big companies. Generally, everything gets scaled out as you go along, but it all depends on the solution or the project. Deployment is obviously quicker with the cloud version. It goes a lot quicker, and it is a lot more secure.

This solution was already in place when I arrived, so I was not a part of the initial setup.

The initial setup is straightforward. It used to be more difficult, but it keeps getting easier. The time it takes to deploy the solution depends on the project and could take a full day, but I have had a client in which deployment took an entire year. 

For deployment and maintenance, it depends on the size of the company, but you would most likely need only one to two people. 

The initial setup of this solution is easy, but we have to set up the servers.

The deployment of a basic SharePoint site will take only a few minutes. If we need to do some customization then it will take longer and depend on the requirements.

When it comes to the installation, Microsoft has made that fast and efficient. You really do not have to do anything special to get going with the product. Everything is browser-based.  

The initial setup was straightforward and easy.

The initial setup is very straightforward. It is user-friendly.

We go through the tutorial and you will be able to do everything. The only problem is when we are migrating from legacy to Microsoft. There are a lot of problems in this there, those things are worked out by Microsoft.

It took almost six months to roll up.

The initial setup is very straightforward. It's answering through a wizard a few questions such as the time zone and the amount of space you want to allocate to SharePoint. You're pretty well right off the gate and ready to use it in less than ten minutes.

The planning was a challenge because in Turkey we have problems finding good architects, not just for SharePoint but for any solution. We solved this by asking for support from Microsoft.

While the solution was not complex to set up, I did find that it had a medium level of complexity, so it wasn't quite straightforward. The online version is a bit easier to manage than the on-premise version.

The solution is like a CRM, so the initial setup is complex. It takes a few days to deploy the solution and the length of time depends on how large the company's topology is and what the client's demands are.

The initial setup is complex. Coming from a standard deployment, you still need to take significant steps to make it really shine within your organization. You need to implement it in a certain way to make it useable.

Most of our customers are enterprise customers. For enterprise customers deploying SharePoint, the setup is quite complex. If you don't know what you're doing, you can get yourself into trouble very quickly if you have a lot of data or users. It's very simple when you have a pair of small deployments. Then you can just click next a couple of times to engineer a solution. It's quite complex, however, if you have lots of users or you have terabytes of content. If you have a complex deployment, it gets very tricky and you have to get people who know what they're doing to be able to deploy even though there are challenges.

That's another big problem with Microsoft SharePoint because there was nobody to warn us and tell us at the beginning that, for enterprise deployment, we needed to think very carefully about certain things. It took us some time to build the competencies to understand the tricky areas. We had to learn what to do about performance and so many different things on an enterprise level.

The bottom line is that SharePoint is indeed for complex deployments. You just have to get the right team to be able to deploy it properly.

The initial setup is straightforward. Deployment takes anywhere from two weeks to a month.