I work for civil ministries, and we exclusively use Microsoft products because we get them for a low price.
I handle security with Fortinet, and I run virtualization with Citrix. Those are my main tasks.
I work for civil ministries, and we exclusively use Microsoft products because we get them for a low price.
I handle security with Fortinet, and I run virtualization with Citrix. Those are my main tasks.
Microsoft has many consultants who can provide support.
Some of the Microsoft implementations of protocols are far from standard. They make their own standards, and you're out if you can't convert to them. With other Unix-based solutions, we had more flexibility to react to special problems we needed to solve. We can only solve the problem now if the problem is solvable with Microsoft.
Similarly, it is tricky to integrate Microsoft Exchange Online if you are in an infrastructure provided by other vendors. We have had an alternative solution to Exchange since 2016, and if we had problems, it was never a problem with Microsoft. It was a problem with the alternative product. The problem is that Microsoft has a standard, and you need to stick to it.
Even if the reason for the problems is Microsoft, the SMTP stack in Exchange is far from the RC of SMTP. If the alternative solution makes extensions to DNS for their active directory and if you use an RC DNS server, you would have problems with some of the records that Microsoft produces. They are not replicated. If you begin with Microsoft, you make everything Microsoft. It is difficult to mix Microsoft with other vendors or with other products. And you get less support if you want to choose a solution other than Microsoft.
Moreover, Exchange Online should work on integration with other services like Teams because when they work together, you gain benefits that other companies might not be able to give you.
I have been using Microsoft Exchange Online since 2012, and we will use it in the future.
We formerly worked with Unix-based mail servers. The positive side is that you're flexible. You could use different hardware. You get limited with Microsoft.
Microsoft solutions are expensive.
I prefer to use solutions like LibreOffice since they are free and cheaper, but our partners might have problems reading our data, and we would face difficulties cooperating.
The main problem with Microsoft products is that we get very dependent on them. Until 2016, I had to make decisions for the budget for the Southwest of Germany, and when you work with Microsoft, your budget is fixed to them, and you lose your ability to work with other solutions. That was a bad situation for us.
If you don't plan to use other solutions in the future, it's a good product. Otherwise, you have to be prepared that some problems may arise. Once you get married to Microsoft, it's a fierce divorce if you want to leave. I rate the solution an eight to nine out of ten.
We are primarily using the solution for Office 365 and various other Microsoft products. It's used for any integration of any applications. Multiple company domains have been configured on a single exchange. It helps us standardize and consolidate connectivity.
We like the standardization we can get across all of our companies. We can put all domains on one exchange. The user can then have one single ID instead of creating five emails for one user.
It scales well.
Technical support is helpful.
It's not hard to set up.
The solution is stable.
The product offers good value for money. After a few years, we have seen an ROI.
There are no features that are missing.
We'd like to see more integration with other platforms. We'd like to explore the feature of SSO and Artemis.
I've used the solution for more than three years.
The solution is stable and reliable. There are no bugs or glitches. It's very stable.
The solution can scale well. It's cloud-based, which makes it very simple. We just have to approach our reseller and add on more licenses. You can have 50 users or 50,000 users, and it will work just as well.
We have about 1,000 or more users on the product currently. We do have plans to increase it to 1,500 by the end of the year.
We may have used technical support previously and were able to resolve any issues within a week. They are very good. They are helpful.
I did not previously use a different solution. Past colleagues may have used something else.
The initial setup takes two to four weeks. It's pretty straightforward. We take each domain and consolidate everything on the exchange. We can migrate everything in one go, and usually, we migrate each company each week and migrate one by one, so that end users are not disturbed.
We have experienced an ROI after three to four years.
We pay for the solution annually. The price is a bit expensive. However, it offers good value for money. The implementation cost is minimal. Also, now it is on the cloud, we don't have to worry about storage, maintenance, or hardware. The cloud is highly secure, and it helps save us money in the long run.
This is the latest version. We are using the cloud version, and it is constantly updated. We are using all of the standard features that come with the cloud-based product.
This is a very user-friendly enterprise solution. Everything is very secure according to GDPR needs. The product is scalable, and its offering good value for money. Everyone can use it. It's a great product.
I'd rate the solution nine out of ten.
The primary use case of Microsoft Exchange Online is for emailing.
The most valuable feature is the cloud environment.
The deployment is complex and has room for improvement.
I have been using the solution for five years.
The solution is stable.
The solution is scalable.
The technical support is good.
The initial setup is straightforward.
The deployment takes some time because it is complex.
We required 14 people for the deployment.
We have a three-year license for $25,000.
I give the solution a nine out of ten.
We have 700 people using the solution.
I recommend Microsoft Exchange Online to other users.
The primary use case of the solution is for email and SharePoint.
We are beginning to explore Office 365 Online Exchange and Azure, which are part of Microsoft 365. We intend to create our Active Directory and Domain Controller on Azure and integrate OnTime Active Directory with Azure Active Directory.
I haven't encountered any downtime with Exchange Online so far. Last week, the entire Azure portal experienced an outage, which caused some disruption, but thankfully, we haven't had any issues with 365 yet.
The stability of the solution has room for improvement.
I have been using the solution for over four years.
I give the stability a seven out of ten.
The solution is scalable.
We have thousands of people using Microsoft Exchange Online.
We have a limited amount of time to contact tech support, but we usually communicate with the vendor. If I have an issue, our Microsoft partner can help us with problem-solving.
We previously used Google G Suite before switching to Microsoft Exchange Online.
The initial setup is straightforward.
The implementation was completed in-house with the help of our Microsoft partner.
We have seen a return on investment since we are taking advantage of the license and Microsoft Exchange Online's useful features.
The cost of our annual license for the solution is moderate. I would give the cost a five out of ten.
I give the solution a seven out of ten. Microsoft Azure has experienced outages at times, but it can be comparable to Amazon Web Services (AWS).
I strongly suggest using Microsoft Office Exchange due to its ease of use and maintenance, as well as its increased reliability and added security features.
Microsoft Exchange Online is used for emails and it does a fantastic job.
The only reason why you would choose an online solution is the company that you're working at is they do not want to have an onsite server. The companies that want something on-site would choose the on-premise version.
The most valuable feature of Microsoft Exchange Online is if you have people that are geographically distributed from each other is good. For example, if you have people in the United States, Europe, Africa, Asia, and Australia, having an online solution works best because then you can reach the scale of the data centers that are available by Microsoft. Additionally, if you're only going to have two to three people using the solution the cost is a lot less than having an onsite server and licensing. It is highly beneficial in these areas.
The online archiving option works well. If you have a lot of emails and you want to keep them indefinitely, then you can use the online archive. It's available permanently and you can store quite a bit of email inside it.
I have been using Microsoft Exchange Online for approximately four and a half years.
The stability of the solution is good. I've only had an issue with it once or twice, but that was due to undersea cable damage.
Microsoft Exchange Online is highly scalable.
We have a lot of users using this solution.
The support from the vendor is fine. However, it could be faster, and some of the agents could be more knowledgeable, but it is a large solution, there's a lot of information that the agents have to work with. I can't always expect when I get connected to the first-level agent that they will know absolutely everything. Sometimes there's no replacement for pure experience.
I rate the support from Microsoft Exchange Online a three out of five.
Neutral
The initial setup of the cloud version is similar to the on-premise version. You can have a straightforward or semi-complex deployment. Cloud deployments do not become as complex as the on-premise version, but they can, depending on how it is used.
The deployment of the solution only takes five minutes. It is very useful when deploying from scratch. As soon as you have the domain up and running it is complete and ready to go.
The license for the solution is cheap, but it could be more affordable in the long term.
We have one level two or level three engineer that does the deployment and maintenance of the solution. The online version does not require a lot of people to run it.
I recommend this solution to others and they will not regret it. They should not use other solutions.
I rate Microsoft Exchange Online a nine out of ten.
I don't use all the features of Microsoft Exchange Online. The product helped me solve my issue related to the storage size needed for backup every time.
Microsoft Exchange Online Microsoft is a useful tool for Microsoft Teams and scrum planning.
I feel that there is a need for improvement in the product, considering that there are some concerns with the tool's integration capabilities.
I have been using Microsoft Exchange Online for three years. My company has a partnership with Microsoft.
Microsoft Exchange Online is a stable product. Stability-wise, I rate the solution a nine out of ten.
Scalability-wise, I rate the solution a nine out of ten.
Around 600 people in my company use the product.
My company has not planned to increase the use of the solution.
The product's initial setup phase was straightforward.
The solution can be deployed in a week.
My company requires people with some IT knowledge to handle the product's deployment and maintenance processes.
My company's in-house team deals with the product's installation process.
My company needs to make monthly payments towards the licensing costs attached to the product. I feel that the price of the product is affordable.
My company chose Microsoft Exchange Online over other products since we have a partnership with Microsoft. For our company's business uses, Microsoft helps save costs and offers good support.
The feature of Microsoft Exchange Online I found to be the most beneficial for team collaboration stems from the integration capabilities. Microsoft Exchange Online can integrate with products like Microsoft Teams or Windows Live.
I have seen that Microsoft Exchange Online's dashboard ensures the aggregation of all the integrated items in a single interface. I think my company has to order Microsoft Teams and apply for it separately to be used on a product like Microsoft Exchange Online.
The security and compliance features of Microsoft Exchange Online have impacted our company's business operations as it is a good tool for business needs, and I haven't seen any major issues with it in any of the items provided. I have also not had any negative reviews or complaints about the product from our company's teams.
I use the solution's calendar functions for my scheduling needs. but I don't know how it offers any support.
The tool's integration capabilities were used for the benefit of the management of the areas attached to the solution from a single place.
I rate the overall tool a nine out of ten.
The solution is basically for access and it provides the ability to just receive and send emails. It also works with calendars and contacts and all of that.
The solution works very well. It's one of the best options available. The access it provides is good.
It has an easy initial setup.
Technical support is helpful.
It is scalable.
The solution is quite stable.
It has okay pricing.
We'd like to have the ability to recall emails on the web. I'm not sure if that is available yet.
I haven't used the solution for too long and need more time to see if other improvements are needed.
The cost could be a bit lower.
We've had clients complain about some aspects of Microsoft Bookings. It would be great to have an opinion platform back on Bookings.
I've been working with the solution for six months.
The solution is stable. The only thing that is not so stable is Microsoft Teams. However, Exchange has good reliability. It doesn't crash or freeze.
I love the scalability. I like that I can start wherever I am and scale up or down. I love the flexibility it gives us.
We have about 50 people on the solution presently.
Technical support is great. I've raised some requests, and they were helpful and responsive.
We did not previously use a different solution.
I took part in the implementation process. The initial setup is pretty straightforward and simple.
The deployment didn't take more than an hour.
We have two administrators that are global admins. We have one admin that is specifically for Exchange.
The pricing is fine. I've discussed this with customers, and they have found the price point to be fair. When you compare it to others, like Google, it is competitive. If it could be lower, of course, it would be ideal.
The solution costs $12 to $16 per user per month.
I currently support Microsoft products. I don't sell Microsoft. They also have my test environment, where I test a few things.
Everything is available in the documentation. It's a great solution. Everything you need is there.
Overall, I'd rate the solution nine out of ten. There's always room to improve still.
We primarily use the solution for email and calendar functionality.
It works. It does what it's supposed to do with minimal issues.
It's one of the products that Microsoft has absolutely done its very best with.
The solution is very easy to set up and quite quick to deploy.
Right off the top of my head, I can't think of anything that I would change to improve Exchange.
The pricing could always be better.
Right now, I'm writing documentation to upgrade the existing Exchange and Active Directory from 2016 to 2019.
When you migrate from on-prem to cloud, if you choose to or are forced to do the hybrid, they need to devise a way to undo the hybrid. At present, once you establish a hybrid organization between cloud and on-prem, there's no way to undo it. Fixing that would be most beneficial. At the last organization I was at and did a migration, I had 31,000 users, and my largest mailbox was 90 gigs. It took three months to complete the migration.
We had no choice but to put it into hybrid mode due to the period of time. The MX record can only exist in one place. Therefore, you can't route mail from one system to another system. All the mail had to be routed through the on-prem and then synced from the on-prem to the cloud until everything was in the cloud. Then we were able to move the MX record from being on-prem to being in the cloud. Then all mail could be received in the cloud. However, then there was no way to tear down the Exchange organization on-prem. We are still left with a server, server maintenance, licensing, OS upgrades, patching, and everything on the on-prem server. The on-prem server is literally sitting there doing nothing except filtering air in the data center, costing me power, time and cooling. Therefore, fixing that would be awesome.
I’ve used the solution throughout my career - for over 30 years.
Typically, by the time I open a ticket, and they get back to me, I've figured out how to fix it. I don't call them until I'm really stuck.
They're not very good. I have had one of their technicians call me back more than once, and I'll go, "I figured it out, I fixed it." They flat asked me, "Well, how did you fix it?" I'm like, "You're Microsoft. You figure it out." They may not have the best understanding of the system.
Neutral
I've used Exchange my entire career. My best friend is currently trying to get rid of Lotus Notes where he's at. He's been working on that for a year now, and it just doesn't seem to want to go away. I've always been with this product. I did a bunch of work with GroupWise and got GroupWise out of the environment and so forth - replacing that with Active Directory. However, that really didn't have a mail component to it.
The initial setup is very straightforward. It only took a few hours to deploy.
The pricing is always something that could be better. We always like to work towards protecting our budget.
I know what the cloud cost per user is. I don't have what the on-premises costs are.
I’m a customer. I don't have any direct relationship with Microsoft.
I’d rate the solution a nine out of ten.
It's an excellent product. It's an excellent mail system. It does exactly what it's supposed to do. If you are under 5,000 employees, I would say that Microsoft 365 is the way to go. If you're over 3,000 or 5,000 employees, I would have some serious conversations about on-prem versus cloud. Once you get over about 3,000 or 5,000 employees that are mail users, the cloud really starts to get much more expensive than on-prem.