Skip to main content

Microsoft Cloud, Hybrid and On Premise Options -- Update from the Field

InfoStrat has witnessed growing interest in cloud computing among its customers, but not as much movement as you might expect based on the amount of press received from cloud computing.  Our primary customers are public sector: federal government, state and local government, and education.  These are not usually the first to implement new technology, so they tend to lag behind trends.   Nonetheless, we are seeing solicitations which either call for cloud deployment or request bids for both cloud and on premise deployment.

Another barrier to cloud computing is that government agencies impose security standards for computing solutions, and cloud providers are scrambling to achieve certifications such as FISMA and FedRAMP which are needed by federal agencies. 

Our solutions are based on the Microsoft platform, especially SQL Server, Dynamics CRM, and SharePoint.  Most of our clients own traditional volume licenses for these Microsoft products, and Microsoft affords an unusual flexibility to combine on premise with cloud options. 

Microsoft Office 365 is picking up momentum among our government clients, especially for its email capabilities. 

Microsoft Azure allows our clients greater control over the cloud environment than is available with Office 365 or Dynamics CRM Online.  It provides cloud infrastructure and is a way to get to the cloud quickly but still have control to manage your servers as if they were virtual servers in your data center.  Recently one of our clients chose Azure for its SharePoint requirements because of this greater flexibility to configure and integrate.

We welcome the move to cloud computing because it allows us to provide the same level of performance to all our clients and be less dependent on the unique attributes (and sometimes politics) of their infrastructure. 

Popular posts from this blog

Key Concepts for Microsoft Dynamics 365: Tenant, Instance, App and Solution

To understand Microsoft Dynamics 365 (formerly Dynamics CRM), you need to learn some new terms and concepts that may be a bit different from what you know from databases and solutions that are hosted on premises. This post introduces some of the key terms and how these concepts are important for planning your implementation. While Dynamics 365 is available on premises, it is most commonly deployed on the Microsoft cloud.  This blog post discusses only cloud implementations. Microsoft has multiple clouds such as commercial and government community clouds. We start with a Microsoft tenant .  A tenant is the account you create in the Microsoft Online Services environment (such as Office 365) when you sign up for a subscription. A tenant contains uniquely identified domains, users, security groups, and subscriptions.  Your tenant has a domain name of .onmicrosoft.com such as acme.onmicrosoft.com.  User accounts belong to a tenant, and subscriptions are assigned to user accoun

Understanding Dynamics 365 and Office 365 Admin Roles

Managing Dynamics 365 instances If you run Microsoft Dynamics 365 (formerly Dynamics CRM) in the Microsoft cloud, you need to understand how your Dynamics instances relate to Office 365 and choose which of your administrators receives which roles and permissions to manage Dynamics 365. In on premises deployments, your network administrator would create and delete user accounts.  The Dynamics 365 admin would then assign permissions to users in Dynamics 365. This post explains three administrator roles: Office 365 Global Administrator Dynamics 365 System Administrator Dynamics 365 Service Administrator You may think that the Dynamics 365 system administrator would have power to do all the actions needed to manage Dynamics 365, but this is not the case. What's different in Microsoft cloud deployments is that licenses and user accounts are managed in Office 365 by an Office 365 Global Administrator.  This role is analogous to a network administrator for an on premises

Replacing Microsoft InfoPath with Power Apps

Source:  https://powerapps.microsoft.com/en-us/infopath/ by James Townsend Microsoft has offered a number of forms automation products over the years, and the most long running was InfoPath which was released as part of Office 2003.  InfoPath is a powerful and flexible product that stores user data in XML while offering form features such as rules, data validation, scripting, and integration with SharePoint.  The popularity of SharePoint resulted in many organizations standardizing on InfoPath for forms, especially internal forms which are hosted on an intranet such as employee reviews, leave and payment requests, and human resources forms. Microsoft has discontinued InfoPath, with mainstream support ending July 13th, 2021, and extended support ending July 14th, 2026. Microsoft has named Power Apps as the successor to InfoPath .  Power Apps has much in common with InfoPath.  Both products include integration with SharePoint.  Both are geared toward the citizen developer and do