When you invest in Office 365, the next step is to embark on a successful migration so that your business processes go on without interruption. Many organizations fail to realize just how important this is. Take, for example, an insurance company that just started on their Office 365 migration project by migrating 500 mailboxes per night. Some recently migrated users start complaining that there is content missing from their folders, and their mailboxes are unavailable. The number of help desk calls is rising fast, and the organization is only troubleshooting as a reactive measure. The insurance company sees a big impact on their business line productivity.
An organization’s employees perform millions of actions on Office 365 each day, so it’s important for administrators to have tools to investigate incidents that occur which could threaten the security of the network. Administrators need to be able to find out who is responsible for each incident, and what actions need to be taken to resolve vulnerabilities in your Office 365 environment.
The IBM Domino environment was mostly replaced by Microsoft on-premise technology, and later replaced by the Microsoft Cloud Services. One thing that hasn’t been replaced is the need for administrators to have control and visibility of service delivery to end-users.
Whether you’re using IBM applications, Microsoft on-premise servers, or Microsoft Office 365, as the messaging administrator you need to provide availability and performance metrics of the service delivered to your management. You also need to understand issues when they arise.
So, the word of the year 2016 was “Post-truth. Wikipedia defines Post-truth as getting information from emotion rather than facts.
While this concept seems to be linked with recent political campaigns in the UK and the US (and please remember that we are Swiss, i.e., neutral …), it also pertains to running collaboration servers.
Administrators know that if you don’t show your users how to get value out of Office 365, they won’t take full advantage of it, and your organization won’t truly reap the benefits of your investment. A main issue with Office 365 is that admins have struggled to get comprehensive, actionable information. That’s made it difficult for admins to measure Office 365 service adoption, and even more difficult for them to share that information outside of their teams due to limited sharing functionalities.
A good storekeeper prepares his shop before opening each day, and cleans it up at night for the next day. Why should your organization be any different? Running daily health checks ensures that your end-users have a good experience when ramping up in the morning, and that they don’t experience any outages throughout the day.
In this day and age, the majority of business transaction processing happens in the cloud, or is consumed as a service from various locations around the globe. If you’re just monitoring your infrastructure back-end resources and systems availability, that’s not enough.
In order to ensure smooth enterprise operations, it’s crucial to monitor the service delivery of your applications. The perception of your service delivery quality may be different between corporate sites, or vary between continents. Your application could be perceived as way too slow by end-users in a particularly strategic region of the world for your business. Once you start objectively and systematically measuring availability and response times, you can begin ensuring the highest possible performance and quality of service to your end users.
It took us a little below two years to have our first Gold version out. Needless to say, GSX Gizmo is more than just a pretty face. There is behind it a number of technologies that we have already deployed and some which will come out later (I have to keep some mystery about this on purpose).
The most important elements are why we developed GSX Gizmo.
An unorganized, cluttered Azure Active Directory should be an Office 365 administrator’s worst nightmare. For one, an AD that isn’t up-to-date can create security risks. If you have unused accounts that should no longer be in Active Directory, it can make your organization more vulnerable to threats. Verification becomes nearly impossible, which leads to security issues that could impact the entire organization. Making sure to delete, disable, or move unused accounts can help keep your Azure AD organized, preventing security threats and making your Office 365 environment more manageable.
Active Directory is a critical component in most distributed and hybrid cloud environments. The foundation for Office 365 deployment is identity, so whether you’re using simple cloud IDs or synchronized IDs connected to your local Active Directory environment, you must provide a login for each user. Azure Active Directory is what’s used by Office 365 to provide access to services. Each user is unique in Azure AD, and you can’t synchronize a single user into multiple tenancies using Microsoft’s supported methods. So, when you throw in multiple tenants for your Office 365 environment, several roadblocks can present themselves.