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.
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.
Delivering an excellent end-user experience is important for IT administrators, and interruptions in application performance (like your email going down) can create headaches for all involved. Microsoft launched Office 365 with the promise of high availability through its financially-backed service level agreement (SLA). This was designed to give organizations the freedom to focus on other areas of migrating to the cloud, but not all organizations have been quick to fully maximize their cloud investment.
Organizations often face problems moving to Office 365 because of Identity and Access Management (IAM) issues, which are usually related to Azure Active Directory. IT administrators face many scenarios when it comes to deployment and maintenance of IAM strategies in complex hybrid-cloud environments. Here, we’ll discuss some of the challenges involved along the way, and how to control your access management in the cloud. Identity and Access Management describes the process of controlling who has access to what within your cloud environment. With Office 365, IT admins create and manage users in the Admin Center, then accounts are stored online in Azure AD.
More than 23 000 people attended the yearly Microsoft Ignite conference at Atlanta last week.
This is a huge turnout and the organization, logistics… were professional. Even the Wifi worked flawlessly … The only little negative was the food located at inconvenient places in the center. However, this enabled us like many attendees to quickly drop in at the CNN food court. So many – and I am sure you as well – could not resist when arriving practicing your James Earl Jones voice and attempt to say with a deep voice: “this is CNN” (OK and we said “This is GSX”). It was also fun for us coming from Switzerland to be able to feel the heat of the first Presidential Debate.
Businesses rely on authentication and identity management to ensure user’s processes are structured, secure and efficient. For organizations using Microsoft Exchange on premise, making sure that the Active Directory server can authenticate users is generally enough to guarantee the identity service. However, the rise of Office 365 has made identity management much more complex. With Office 365, the on-premise Active Directory has to work in collaboration with Microsoft Azure AD Connect and Active Directory Federation Service (ADFS).