Office 365 Reviews

We use it throughout our business for email and documents. It has allowed us to stop maintaining SharePoint and Exchange installs.

It has allowed us to eliminate a lot of in-house infrastructure and has simplified our software licensing.

Cloud-based management is valuable and software deployment is positive. SharePoint, document sharing, and Skype have been helpful as well.

They should stop releasing new features and focus on making the existing ones work. Their support is so terrible and unusable except during dire emergencies.

• Exchange Online
• SharePoint
• Skype for Business
• OneDrive

• Removed support and infrastructure of legacy technologies.

Be sure you understand ADFS and, if you decide to go with it, what you get and don't get with it. Your users will want it.

ADFS was sold to overcome the issues with entering passwords in all your clients (Outlook, Skype for Business, OneDrive) but, if your password changes, you do have to manually update passwords in all of these clients.

Also, this does not get you direct access to the 365 portal or SharePoint without modifying links to use Federated Services.

This becomes an issue if you use generic accounts for the shop. It will work if each of your users are required to use their own ID. Also, note there is a cost for the Azure instance of ADFS (servers, compute, network, VPN).

I have used it for nine years.

Deployment went very smoothly even in its infancy. My most recent deployment went off without issue.

Others report stability issues and there are often warnings in the console but the service has been flawless for us.

We have not encountered any scalability issues. We have probably increased our user base 20% since inception.

For general support, it is offshored and you open a ticket in the console. It works pretty well. For how-to's or best practices, you will need to have a good partner.

Generally, the technician has a good idea what you are trying to do. There is often a handoff to a group that can actually DO the work.

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

A vendor team implemented it. I would rate them 10 of 10 at the time. Since then, our resource has moved on but they still have a pretty good skillset.

I don't have my spreadsheet handy but the ROI was there. Microsoft also provided significant incentives to make the move.

If it is an in-person query or reference, I do let them know the deal I got, as well as the approach that got me there.

Because of the significant investment we already had in Microsoft, this made the most sense; thus, I did not evaluate competitors.

You may need ADFS; you may need a hybrid environment. Not everything necessarily goes away. Also, user management continues; it just moves to a new place (hosted/the cloud).

Our primary use is for email.

The most valuable feature is Microsoft Exchange.

The security should be improved.

I have been using Office 365 for about four years.

It is a stable product.

It is scalable and easy to expand to more users. We have 200 people in our company who are using it.

The technical support is very good.

Overall, this is a very good product.

I would rate this solution a nine out of ten.

If you have a global solution, you can go from one product to the other very easily. And then you can share data between all the different Office tools which is good because participation and sharing is very good. That's the most important aspect of Office 365.

I have been using Office 365 for four years. 

We don't have any problems with scalability. We have around 150 users. 

We have an internal IT support team. So we send any problem to IT support and they contact Microsoft if needed. 

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.

I would recommend it because it's rather user friendly and we don't have any particular problems. I would recommend it to a company without a problem.

A need that a company like ours has is that we want to be able to have data flow into one tool, for example, for all the management of tasks through the company and workflow of who is doing what and so on. There are no real solutions for this at the moment in Office 365. It would be nice if they could implement this in the next release, so we can have one solution from one company giving us the whole data and flow of data into the company.

I would rate Office 365 an eight out of ten. 

We use this solution for email exchange.

There are several areas that this service can be improved. The email, there are certain features we would like to see improvements from Microsoft, and also there are applications called BlueJeans, and there are certain things.

There are several additional features we would like to see, such as advanced features of SAN protection in Office 365. The main thing is the SAN protection; we would like to see a lot of advanced features added because we had a lot of spam attacks.

It's very stable.

The scalability is good. More than 700 people are using this solution. Their job titles range from IT manager, network engineer, to corporate team members, there are several staff engineers, everyone.

We have about three people who are directly working with deployment and maintenance.

We were using open source email server entourage exchange, and from there the best option was to migrate to Office 365.

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.

Technical support of Office 365 is good.

We are using a particular type of license which allows each item to be priced around 30 dollars per month. There are no costs in addition to the standard licensing fees.

The advice I would give depends mainly on their requirements. If they need to minimize their administration, Office 365 would be an excellent option.

On a scale of one to ten, one being the lowest and ten being the highest, I would rate this product a seven.

Our primary use case is for creating files, and typing projects and for converting Word documents to PDF format. 

Most of the work that seems not to work offline works perfectly with Microsoft Office 2013, like converting a Word document to a PDF file. 

The ability to convert Word documents to PDF file is one of the features I love most. Pictures can be pasted into the Word environment and can be converted to PDF. 

The feature to convert PDF file to a Word document needs improvement as well as the feature to save the file automatically when typing, without using the save command. 

It is efficient and effective. 

The scalability is really good. 

The technical support are responsive. 

We previously used a different version, Office 2007.

The initial setup was not really complex. 

The installation was done in-house. 

The pricing is not really high, but one can get the software with the license key for free. 

I like quite a few of the applications included in the solution, including OneDrive as well as Teams. 

The solution offers all of the Office features, that we have access to and can use whenever we need to. 

The solution can be accessed from anywhere. You don't have to be in the office or at your desktop to use it.

The solution is quite intuitive and easy to use.

I'm not sure if there are areas of improvement. For us, it's working quite well.

I've been using the solution since the original launch of the product itself. I'm not sure how long it's been. I believe it's been about ten years or so. It may have been since 2011.

The stability of the solution is great. We don't have any bugs or glitches. We don't have it freezing on us. It's reliable.

The scalability is okay. However, we have such a large organization, and because IT has to enact it, it takes a while to do each one by one. In order to scale, a company simply has to buy more licenses, so, from that perspective, it's easy. 

I never deal with technical support directly. We have an in-house IT department that we go to when we need help or have issues.

For example, iinitially I had some issues with the setup of Office 365 on my mobile. However, it wasn't an Office 365 issue. It was all due to some of the company's internal security policies. Our own IT team procured the licenses, so they dealt with the issue, meaning I never had to actually go back to Microsoft for that or make a call to them.

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.

We're just a customer. We don't have any business relationship with Microsoft.

We're using the latest version of the solution.

I'd recommend the solution. It's very easy to use and extremely practical. We find it quite useful within our organization.

We don't use any comparable products, so it's hard to rate the solution in comparison to alternative offerings, however, generally, I'd rate the product nine out of ten.

I am a business consultant and have worked in business continuity for about eight years. I work for factories, banks, government, and other organizations. I use different methodologies that depend on the customer's requirements.

I have found that Office 365 is one of the best tools for business continuity, for small companies.

Many of the features in Office 365 are good, but I think Excel is a very good tool. Excel is good at processing data in small volumes. 

Using Visual Basic, I have had a lot of trouble with relative paths when programming for Excel, and sometimes it is very difficult to debug programs. For example, if the user has their focus on a different sheet, one that you do not expect, then the program begins to behave unexpectedly. This means that you cannot use relative paths, and you have to use absolute paths. Microsoft could issue warnings if you are programming in a way that might have side effects.

There is a problem with the Microsoft Office documentation in terms of undocumented features. When you are programming and there is an undocumented and unexpected behavior in the background, it can be very painful to find the bugs.

The stability depends on what you expect from the solution. For example, I have had some bad experiences with macros in the cloud version, and I am in the process of figuring out why. Simple macros seem to work well when it comes to storing data in the cloud.

We use Excel to do business continuity for small companies, with perhaps one hundred employees. There are usually four or five people who need to use the tools.

For larger companies, with use other tools because it is easier to manage.

We have not dealt with technical support because there are no issues that we could not solve using the knowledge base.

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

Microsoft Office is a basic tool in consulting. I have implemented macros, specialized Office tools, and applications for it using Visual Basic. I usually need to design tools for our clients, because I want to give them a really good product. It needs to be more than Excel, alone, because it has to be easy to enter data. There are also calculations that happen in the background, and we do not want the client to be harassed by things that they do not need to know.

The mission of the Office is to do small computations. It is a tool for small documents and spreadsheets, and I think it's perfect for what it's meant to be. On the other hand, there is always something that can be improved.

I would rate this solution a four out of ten.