We did the setup in a phased approach, where we went out and did our research and then once the tenant was assigned to us, we went through, and built everything. As we got close to releasing, we send out a notification to all of our users saying, "Okay, effective this date, this is what the new processes are going to be." We sent them out in the documentation. However, first, we had to do the research and get everybody together.

We had done a corporate merger. We were merging two companies together. My company had one email system, while the other company had another email system. That's why we had to go through all of the procedures for migrating the other company over. We had to go through all the procedures on how to migrate their data from the Ntiva server, which had all the personal drives. We had to have all that stuff in place for the users.

We did our migration from GCC High over to the commercial side and then, once we were all set up and ready to go, we initiated cutoff dates when we needed to stop using the previous portal. 

We had spent probably about two to two and a half months setting up the backend to get Intune in place and to get all of the data properly cataloged. 

We're still in the process of getting things set up as there are new technologies that come out or changes to the admin sites. We're implementing those changes and we're going through making whatever adjustments we need to make. Now that we've got the endpoint protection and more monitoring, we're seeing how that's going.

One of the drawbacks that we found out was that when we were putting out new policies to the machines, each machine operator actually reacted a little bit differently due to the fact that we did have a couple of Windows machines and a couple of Macs that we did our testing on. Once we felt that we were good, we pushed everybody out, pushed all the settings out to the security groups that we'd set up. Things didn't go as smoothly as we'd anticipated as some machines went flawlessly and some machines were rebooting constantly as they were processing stuff. It was interrupting people during their workday. It works great in dev tests, however, as soon as you put it into production, the reactions are totally different.

Overall, it was definitely a successful migration with just a couple of challenges. 

One of the big benefits of it was that it really made us understand the system a lot better. We had some older machines. It made me realize, okay, this machine is way outdated. We need to update this machine.

We just had two people that handled the deployment process. 

The initial setup is straightforward. You simply purchase a domain and assign it to the platform. If your domain is registered with one of the hosting platforms, such as GoDaddy, they have integration with GoDaddy, you can use it at the same time. With your GoDaddy login information, the process is going very smoothly. I didn't notice any difficulties with the setup.

I wasn't involved with implementing Office 365, but it should be complex when you do it right because 365 is constantly evolving. You have to look at your tenant: Are things new? Are they open? Is it a security risk? What has Microsoft opened? Do I want to let all colleagues access the new features?

It was quite easy considering our expertise, which was not very high. I trained my team thanks to Wiki and online documentation. It was okay. We did not use any partners.

Office 365 is very straightforward to implement.

The initial setup is easy because it's online. You pay for it and you get it, and that's it.

The initial setup for Office 365 was straightforward.

Initial setup is very easy.

Very easy, no third party support is required. Microsoft services team will definitely help you in this with a single service request (at least the basic setup).

The setup has been pretty simple and straightforward. We haven't had any issues. It's not overly difficult. 

Setting up Office 365 is straightforward. I use it on Mac and Windows, and it only takes a few minutes in both cases.

The initial setup was straightforward. We followed the instructions. Since it's a cloud solution we just opened the administration tabs and created the rules as they apply to our operation. We created XML. We did have to build some code within the solution.

Deployment took a few months to fully implement the solution. The strategy we used was to test the solution within a test account first and after that, we deployed the products and we selected a subset of users to deploy it.

The initial setup is very straightforward. It’s not complex. It’s not difficult.

The last time I set it up, it was pretty straightforward. This time, to be honest, I had an external company set it up.

I didn't handle the initial setup. I can't speak about if it is simple or complex to execute.

The initial setup was easy and our team handled it by themselves. MS support gave some advice when needed. 

The setup of Office 365 was straightforward because I'm the one who did the initial setup as my background is in web dev. Additionally, starting the configuration was pretty easy for me.

A hybrid deployment of Office 365 took approximately two days to have all their emails migrated and everyone up and running.

Initial setup was very straightforward.

The initial setup was straightforward. It wasn't complex at all. However, I'm used to working in the Microsoft environment.

I'm not sure how long deployment actually takes.

The initial setup of Office 365 is straightforward and very easy.

It is a very easy, logical set-up and now they have an on-boarding wizard which looks helpful and offer FastTrack to help with on-boarding.

I would not say that the initial setup is complex. Rather, it is of medium difficulty, somewhere between straightforward and complex.

Once we decided to use Office 365, we were able to onboard people seamlessly. We were able to quickly start working with Team, Skype, and other products.

The initial setup for this solution is very easy.

The initial setup was straightforward. I think deployment took around one and a half months. and the strategy was to get a batch of users first migrated to Office 365 and then continue in batches until everyone was on board. We worked directly with Microsoft for the deployment. 

The non-changeable primary tenant DOMAIN.onmicrosoft.com was not explained clearly to me back then. I wound up opening a few instances, instead of adding multiple domains to a tenant. But what still has not been resolved are the branding issues, i.e., if your brand-expressing domains are not intuitively related to each other. For example, there is no mbamoralist.com yammer network b/c my primary domain is succelleratorsaas. If one legitimately owns the domains, one should not be locked into decisions about brand primacy that may have applied at that time but don’t today.

The installation was not complex. Everything required a series of steps and checklists to follow that allowed the implementation to come to a happy conclusion. The concern is to make sure that there are additional resources available when the implementation ends. This could be a high number of resources.

The initial setup is not complex at all. It is very straightforward, in my opinion.

Our central team rolled it out, therefore I wasn't part of the deployment process. I'm not sure how long it took to roll everything out.

I'm not sure how many people are needed to maintain the solution.

The initial setup was okay. It was not too complex, but it also was not as straightforward as it might have been.  

The initial setup was not too complex. 

It didn't take any time. It just happened to be working from when I first connected, I did not have to do anything.

On my HP laptop, it came with the computer and it was supported by acquiring a license. I update with a license through Best Buy, for the software itself for the MS Access or for Word. Now with my school, the only way to be aware of Office 365 is when logged in as a faculty. Then we're using the software that they have provided and it's through a connection. It's not on the machine.

It is very easy to deploy.

Our vendor assisted with setup using the Jump Start program. There are complexities with certificates, hybrid, etc., but overall, it went well.

I'm not the one doing the setup, so I don't know exactly how long it takes and if it was difficult, but I think it went quickly.

The initial setup was a bit complex because we were migrating to exchange service. 

Deployment took around three weeks to fully migrate everything to Office 365.

We used official applications provided by Microsoft for the migration. There were no other articles used.

The initial setup was not really complex. 

The initial setup was not complex at all. It was easy for our organization. The implementation is something that is taken care of by the end user's IT team, so I didn't actually handle it myself. Once it's set up, it is easy to use. It's not very difficult; everything is clear. Once you start using it, you'll see it's a very good tool.

The initial setup is simple. Once you enter your license key it is done. An unskilled person with no IT background can install it.

The initial setup was straightforward. The process was short. I did it myself. 

Initial setup was not complex.

The initial setup was not complex. It was very straightforward. We were online in a matter of minutes.

Deployment has taken about two and a half years.

The initial setup is very straightforward. There are some complexities to it if you use some of the more advanced features, but for the basic install, it is very easy.

Easy.

The initial setup is very easy.

The setup is easy and user-friendly. On-screen guided instructions help make the complex process easy to use.

Initial setup was very straightforward; was able to set up and migrate with little assistance.

The initial setup is straightforward.

With the help of a clear project plan and adoption plan, implementation of Office 365 is mostly straightforward. SharePoint does need more attention. Mostly adoption issues.

It was easier to set up in the earlier versions. Now it has many more bells to ring.

In our case, the installation was fairly easily, after good preparation and a plan of action. The migration of all old mailboxes to Microsoft Office 365 takes a long time. We completed this with no problems.

The initial setup was straightforward.