An enterprise-grade configuration management system that provides controlled access to software assets.
N/A
Microsoft Entra ID
Score 8.9 out of 10
N/A
Microsoft Entra ID (formerly Microsoft Azure Active Directory or Azure AD) is a cloud-based identity and access management (IAM) solution supporting restricted access to applications with Azure Multi-Factor Authentication (MFA) built-in, single sign-on (SSO), B2B collaboration controls, self-service password, and integration with Microsoft productivity and cloud storage (Office 365, OneDrive, etc) as well as 3rd party services.
$6
per user/per month
Microsoft Intune
Score 8.3 out of 10
N/A
Microsoft Intune (formerly Microsoft Endpoint Manager), combining the capabilities of the former Microsoft System Center Configuration Manager, SCCM or ConfigMgr, is presented as a unified endpoint management option. Microsoft Intune is an endpoint management solution for mobile devices, an MDM solution that allows the user to securely manage iOS, Android, Windows, and macOS devices with a single endpoint management solution. The component Endpoint Configuration Manager (the…
User experience (user friendly) is easy then google workspace.Licensing cost management also easier then google platform. SSO and MFA work much better and easier then GCP. Integration with third party software we can do using online video learning in Intra id. apps are work …
Okta has no chance to compete with Microsoft Entra ID's features. Also the usability of microsoft products and user management is easier when you have one product that does almost everything.
We had implemented Okta previously and had a great experience with it. I was not involved in the setup or admin but did deal with end user support during that time. We made the move to azure AD since it made the most sense for our environment, and to have fewer spices in the …
As much as its easy to compare AzureAD to others, as much as it gets complicated. AzureAD is a direct choice for business relying on the Microsoft ecosystem of products and services, the integration between AzureAD, Windows and Windows Server is phenomenal, and Microsoft keeps …
In our particular scenario, we chose [Microsoft] Azure Active Directory because it has integration with tools and applications we use on a day to day basis, such as inTune, Autopilot, Office 365, Exchange Online, Dynamics 365, just to named a few.
Google Cloud was the only other main contender for us. However, it was a logical move given what we were already paying for in Microsoft licensing. Additionally, the feature set of Microsoft Azure Active Directory is simply more robust than what is offered from a Google …
I've worked with both Okta and Auth0 at various clients. Consistently, we find that Azure Active Directory provides a more seamless experience, better integration with IT tooling, and a more developer-friendly experience. In the past Azure AD has lacked some of the …
Group policy, the predecessor of Microsoft Endpoint Manager was a great, easy to use tool. It is dated and stuck as an on-prem solution but still very good and served a purpose. We are still using this in conjunction with Microsoft Endpoint Manager whilst we complete our …
Microsoft System Center Configuration manager was always selected because it combines several standalone solutions provided by other vendors. Has great integration with all Microsoft services including Azure. Being an enterprise standard level product, you can expect that your …
Microsoft System Center Configuration Manager does not have any competition. None of the other deployment solutions have the amount of features SCCM has. SCCM has loads of templates, stronger third party support, and a very big user community to help you troubleshoot your …
IBM Rational ClearCase might be better suited for a smaller / simpler code base. Larger code bases really slow it down... but then again there are better alternatives out there for source control
If you have a mixed solution, such as different types of devices with different types of operating systems, it could be more complicated. But if you have already decided that your company will be a Microsoft company in terms of everything internally running with Microsoft software, like the operating system, Windows 11, then this is probably the best way to use it. So if you have mixed or hybrid solutions or scenarios, maybe it's not exactly what you mean.
Microsoft Intune is well suited for the larger end of the small business segment to the enterprise. The ability to configure and remotely deploy computer configurations, control mobile devices, and fine tune security controls of each device or device group is a major win for this product. Smaller and mid-sized businesses may balk at having to increase their license level to unlock the better updating features.
Rational ClearCase is excellent for handling versioning and branching. No other tool I've used has the depth that ClearCase has when it comes to handling complex branching scenarios and identifying where certain versions of particular files are within a particular configuration.
Rational ClearCase handles parallel development of many dependent applications really well.
The use of ClearCase Views to switch between projects and configurations is extremely convenient as opposed to the local workstation model of the competitors.
Many people at our company work remotely, including the sales and procurement teams. So people usually travel from one country to another country. Some people travel to Australia or some people travel to Canada based on the business requirements. So we usually audit the sign-in logs and verify whether the user is valid while they're using our company's email ID to perform their day-to-day operations.
[Microsoft Endpoint Manager (Microsoft Intune + SCCM)] helps to speed up the deployment of patches/software throughout our environment. I can easily build a package and then deploy across all endpoints.
The ability to supercede software is also quite handy. This automates the removal of old versions and replacing them with newer versions.
The Intune Autopilot option is very useful if you want to deploy software to devices straight out of the box. You can configure them to download software when a user opens a new PC and turns it on for the first time.
I say "cost" on a per-user basis for smaller organizations, which is why Microsoft has small-business programs. I'm trying to figure out if anything is uniquely gripping. I guess transitions to and from, but to be honest, that's where we live. The difficulty of adopting Microsoft Entra ID when you didn't start there as an organization is a little bit sizable, but that's the case with any identity provider. It's not anything endemic to Microsoft Entra ID. It works. It's efficient.
Deploying more apps besides Microsoft Edge and Microsoft Office 365 app
Microsoft needs to make it easier to deploy exe, pkg, and msi apps without having to go through the manual process of re-packaging these apps using tools from github like intuneapputil
Add a feature to push out software updates for 3rd party apps
MSFT Entra ID has been essential for managing our geographically dispersed team. We're confident that it will scale with us as grow, and we'll be able to take advantage of additional security and ID management features as they become necessary. Being able to centrally manage our user access from anywhere with a small support team is such a relief.
Mascom Wireless is a Microsoft shop and SCCM has proved to be helpful in keeping our Microsoft products up to date every month without fail. We also have a Microsoft Enterprise Agreement which we renewed for three years ending 2022. The remote access utility works wonders for the organisation and have saved travel bills including subsistance allowance. We have been able to fulfill security audits both internal and external. We have been able to keep a robust inventory of our computer assets and nothing falls of the cracks
Simply because of what I mentioned earlier, the feature set sort of keeps changing and they do a lot of, they integrated with a lot of the other tools and so for users who are not as well seasoned, it may be a little bit more complicated for them to begin working within the tool.
The console is not intuitive and does not work well often. Due to the complexity of the product, documentation can be confusing. When properly configured, routine tasks like OS deployment, remote control, and software deployment are easy to do. Troubleshooting of System Center Configuration Manager issues is hard, as there are various logs, and their content can be hard to understand.
It's a 'heavy' system, which demands a lot of resources form the datacenter perspective. So, make sure you followed the requirements to avoid frustration in the future. From the 'client' perspective, it's fine. I've never had any issue with that.
I have not needed to engage support for anything at this time. I have been able to find the answers either online or in a knowledgebase. I tried to skip the question but it would not let me, so I rated a 9 based on other interactions with Microsoft support I have had
We have not needed to seek support for this product in the time that we have used it thus far. It's been working really well, and have not had any major issues. Being that it's a Microsoft product, it goes without saying that there will be many support options available if needed. This includes phone, web, forums, KB articles, etc. There is even comprehensive documentation that is available on the web through Microsoft's website for use of the product.
Make sure you use a good partner. Our implementation was a bit longer and more problematic than we expected. Our partner got it done, but, in my opinion, some of their inexperience and staffing issues were evident.
Work with a "test group" of users who you have a good relationship with so that when things don't work properly they understand! Work with your partner nicely without forcing things especially timelines as you are bound to make mistakes and create oversights in the project Management can also interfere with the implementation (which can cause delays) if you make too many mistakes which takes me back to having a "test group" where you have good relations
If development is centrallized to one location and your company releases hundreds of customized versions of your software per year, then ClearCase is the best tool for managing the complexity of multiple versions of customized software. If your company has globally distributed development, then I'd recommend Team Foundation Server over ClearCase. If your organization uses Agile Methodologies, then I'd recommend TFS with GIT.
Microsoft Entra ID is not as stand-alone product as competitors like Okta. It may lack some of the features that competing products have but on the other hand it integrates both technically and license wise with other Microsoft cloud services and is easy to deploy. It is also the easiest way to extend identity management to the cloud if you already have Microsoft Active Directory in use.
We did not evaluate or use other products like Microsoft Endpoint Manager (Microsoft Intune + SCCM). The main reason we did not evaluate or use other products is because Microsoft Endpoint Manager (Microsoft Intune + SCCM) integrates seamlessly with Microsoft 365 and Windows PCs. Expenses would have increased as well if we had purchased another similar product.
Microsoft Professional Services' technical knowledge is appreciable as consultants design the solution as per customer requirements. Mapping of features per user specifications and assisting Customer IT engineers to implement so they can manage and administer the services.
I think managing costs was probably the biggest one as a nonprofit. We're always worried about the financial impact that any product can have. And as licenses change or they are shut down, migrating to the proper product without going over budget is always something we are concerned about. But for the most part, it's been positive. Microsoft works for us as nonprofits to make sure that we get very fair pricing.
In our current environment, this System Center Configuration Manager had replaced several standalone solutions for patching, imaging, remote assistance, reporting, etc. That saved a lot of time and resulted in money to manage the IT infrastructure.
Once SCCM is deployed and fully configured, all agents are deployed and it is easy to automate a lot of processes and just control them from time to time to make sure that everything is working as supposed to be.
SCCM + Windows 10: great built-in endpoint protection solution. As a result, there is no need to buy additional software for that purpose.
The imaging process is better compared to WDS because you can modify deployment packages and apply patches to a newly imaged machine. This saves tons of time for new employees deployment.