Every cloud migration follows the same general path: assessment, optimization, security protocol, and management. As your cloud environment matures, the latter three phases should be repeated to refine and improve your operations.
One native Azure tool that can be useful to begin this cloud journey is Azure Migrate. It consists of Azure Server Assessment and Azure Server Migration. Assessment is a discovery tool helps you assess cloud readiness and collect valuable intelligence about your virtual machines and associated infrastructure so you can be prepared to replace them in Azure. Migration, as you might expect, can actually migrate those servers to Azure.
Within the Azure Migrate hub are also database migration tools, Movere (an assessment tool purchased by Microsoft), a web app migration assistant, and Azure Data Box which assists with large scale data migration without using the internet.
This blog will focus on the Server Assessment tool, which helps you plan for cloud readiness, budget, and target environment architecture within Azure. Learn if it will work with your target environment, what it reports, and how it can lay the groundwork for a successful migration.
Two major enterprise computing platforms are reaching their end of life this week. Tomorrow (January 14th), in fact. While this may seem like a last-minute blog entry, we know there are plenty of you out there still running Windows 7 on corporate desktops and Windows Server 2008 or 2008 R2 in your data centers.
Microsoft itself estimated that 60% of its Windows Server install base was still running 2008 back in August. Some of those instances may have been upgraded or migrated to cloud VMs, but we’re betting many of them remain. Unofficial estimates peg the number of Windows 7 machines worldwide at around 200 million.
Change can be hard, especially when your systems seem to be working properly and upgrading appears to be a complex and time-consuming endeavor. But operating systems that have reached End of Support open the door for vulnerabilities, bugs, and incompatibility with newer infrastructure. They also make it more difficult to deploy and support newer software that can improve employee efficiency and empower the business to drive revenue in new areas and to compete with others in the industry. With Windows 7 and Windows Server 2008 End of Support upon us, what are your options?
Green House Data was onsite last week at Microsoft Ignite. We had some incredible conversations at our booth about Azure, PowerApps, application modernization, DevOps, Windows Server end of support, and more. Of course, while we were working the floor, Microsoft made a bevy of product announcements around core products and services that are sure to shake up your IT world! I’m super excited about these new developments, so here are my top takeaways from the show.
A fundamental building block for your successful adoption of cloud services is the organizational hierarchy, a mode of organizing your cloud services, resources, and virtual machines in such a way that you ensure cloud governance and can better resolve billing within your organization.
Cloud governance is the answer to common questions like:
• “How do I keep my data compliant with industry regulations?”
• “How can I implement chargeback within my organization so I know which departments are consuming cloud services and account for that usage?”
• “How can I mandate security and access measures across our cloud environment?”
By implementing a flexible set of controls and overall organizational hierarchy within Azure, you can enable adoption of the cloud services your business units require and avoid shadow cloud use. A well-designed enterprise cloud environment can accommodate modern agile practices alongside traditional workloads.
Here’s how to structure your organizational hierarchy within Azure so you can set governance requirements and encourage speed of delivery for your individual departments and business units.
Microsoft Azure offers native serverless computing features. Two of the most crucial to master are Azure Functions and Azure Logic Apps. Each of them help enable business logic that automates your Azure workflow, but they have key differences and in fact can be used together in a complementary manner to offer flexible, powerful control over your cloud resources.
Let’s take a closer look at how each of these serverless automation platforms work within Azure and some use cases for them.
Microsoft recently revealed a service called Azure Bastion that allows customers a more secure way to connect and access virtual machines (VMs). It uses Remote Desktop Protocol (RDP) and Secure Shell (SSH) network protocol alongside Secure Sockets Layer (SSL) encryption.
Bastion connects VMs, your local computers, and cloud resources without exposing them to public network connections. As a Platform as a Service, it simplifies the process of setting up and administrating bastion hosts or jumpboxes in your cloud environment.
But what are bastion hosts or jumpboxes? And why would you use them, or a service like Azure Bastion?
You would be woefully uninformed and unprepared as an IT admin if you didn’t know that two major Microsoft products, the 2008 versions of SQL Server and Windows Server, are each about to reach their end of support. That means it’s time to upgrade or migrate lest you fall victim to inevitable security vulnerabilities.
One big question when facing a major software upgrade such as this is whether to remain in place, so to speak, and update to the latest version from your current deployment scenario on premise or in a hosted environment, or to move to a cloud-based server – namely Azure, since that offers you tight integration and lower costs with Microsoft products such as these.
SQL Server end of support is imminent, coming up on July 9, 2019. Windows Server has a few months to go, ending support on January 14, 2020.
As you research your options for enterprise productivity applications you likely will come across Microsoft 365 alongside the more commonly known Office 365.
In typical Microsoft fashion, there are an array of different plans and licensing levels for each option. Deciding which is the best option can therefore take some time.
What is Microsoft 365 and how is it different from Office 365? M365 includes enterprise-specific features that you would likely purchase separately, critically several Enterprise Mobility and Security components.
For businesses at the midsize and enterprise levels, M365 seems like the clear choice. But what exactly do you get at each level of M365? And how does it compare to O365?
When using Microsoft technologies in your enterprise IT stack, you have a few native options for systems monitoring and alerts. Two recent product developments — folding Operations Management Suite (OMS) functionality into Azure Monitor, as well as the release of the new SCOM 2019 — have reignited the debate to determine whether Azure Monitor can entirely replace the long standing, good-old SCOM (System Center Operations Manager).
In a way, I feel this comparison is a bit unfair, like comparing apples with oranges. Ultimately the two products can work together and overlap in order to eliminate monitoring gaps in your environment. So which monitoring solution would work the best for your enterprise? Let’s try to figure out!
This is Part Two and the final entry in our introductory blog series on Azure Sentinel, Microsoft's new Security Information and Event Management (SIEM) tool for Azure environments. Read Part One here for information on what Sentinel is, how to set it up, and how to begin importing data from your Azure PaaS and IaaS.
In Part Two, we'll examine deeper functionalities within Sentinel including Machine Learning, queries, and automation.