Skip to main content

Cloud Services Shift Roles for System Administrators



Cloud computing has shifted many tasks away from system administrators who were previously responsible for managing servers which were located on premises or in dedicated data centers.  Many system management tasks such as all hardware upgrades, repairs and replacements and networking issues are now handled by cloud providers (Amazon Web Services, Microsoft,  Google and others).  In most cases, security and other patches to the operating system are performed by cloud providers as well. Cloud providers have been successful in meeting their service level agreements, and set the standard for managing data centers at a large scale with the latest hardware, facilities, and best practices.

Cloud databases do not require the same database administration (DBA) activities, at least for some lower level tasks, but there are still requirements for DBAs to monitor and correct performance and improve data quality. It can be challenging to determine the cause of a database performance issue because the responsibility for the system is spread across several people (and perhaps different companies).

Other system administration tasks remain the responsibility of the customer, such as creating and removing users and assigning permissions.

Cloud computing has changed the way that organizations handle system administration. Because cloud services need fewer administrators, some organizations have eliminated positions or moved system administrators to new roles.  A hybrid cloud environment may result in division of labor among on premises and cloud system administrators.  Specialized skills can also mean that different people manage different cloud services, increasing the number of system administrators.

Troubleshooting may involve multiple system administrators from the customer and cloud providers.  this can waste time and lengthen interruptions of service, especially if incorrect diagnoses ascribe the problem to the wrong admin.

Because Microsoft Dynamics is integrated with Office 365, my clients must ensure close cooperation among system administrators for Dynamics 365 and Office 365.  Usually a department "owns" a Dynamics solution, while the enterprise information technology department "owns" the network and email.  Therefore, the Office 365 admin creates user accounts but the Dynamics 365 admin assigns rights within Dynamics 365 solutions.

I wrote another blog post explaining how Microsoft divides the roles for various admins, but a similar division of labor is applicable for other cloud providers, and even more complex for hybrid deployments with multiple providers.

The best time to find out how your admin coordination is working is before you have a crisis.  It is helpful to create a process for communicating cloud outages to all the admins and have a mechanism for routing support cases to all the admins whose help will be needed to resolve a problem. Otherwise, cases will slip through the cracks or be assigned to people who do not have sufficient rights to resolve them.

Popular posts from this blog

PowerApps Portal: The Successor to Microsoft Dynamics Portal

In case you have been reviewing Microsoft's new pricing for its Dynamics products which was released this month and have been unable to find Dynamics Portal, it has been rebranded as PowerApps Portal and shifted to the PowerApps side of the Microsoft product family.


Rebranding the portal product underscores the importance of app scenarios involving external users such as customers and suppliers.  It also provides a simpler interface than Dynamics 365 for occasional users.

The new portal pricing is based on the number of unique users who log into the portal each month (for authenticated users) and on the number of page views for anonymous users.  "A login provides an external authenticated user access to a single portal for up to 24 hours. Multiple logins during the 24-hour period count as 1 billable login. Internal users can be licensed either by the PowerApps per app or per users plans, or a qualifying Dynamics 365 subscription."

Pricing starts at $200/mo. for 100 dail…

ScreenMeet Remote Support Tool for Dynamics 365 Customer Service

I met Lou Guercia when he was president and CEO of Scribe Software, the leading CRM integration tool.  Scribe was acquired by TIBCO Software in 2018.  I recently reconnected with Lou and learned about ScreenMeet, the company he joined as chief operating officer.   The following is a description of the product provided by ScreenMeet:

ScreenMeet is a cloud-based remote support tool designed to integrate with Dynamics 365 Customer Service. By enabling customer service and IT support organizations to address critical technical issues directly from their CRM or ticketing platform, it streamlines the process and provides a fully browser-based support experience.

You can also use ScreenMeet with other CRM products or even on its own without a CRM.

Here is a short video demo of ScreenMeet with Dynamics integration:


ScreenMeet - Cloud-based Remote Support Integrated with Dynamics 365 Customer Support Once integrated with a Dynamics 365 CS organization, the ScreenMeet widget appears on Case pa…

Microsoft PowerApps and Microsoft Flow Licensing for Beginners

NOTE: Since this post was written, Microsoft has updated pricing.  For current pricing, see https://powerapps.microsoft.com/en-us/pricing

Next month marks two years since Microsoft announced the preview of its Flow workflow automation product.  Since then, PowerApps and Microsoft Flow have been gaining in popularity.

We at InfoStrat are receiving more questions from customers on how PowerApps and Flow are licensed by Microsoft.  This is a brief overview with links to authoritative Microsoft resources with all the details.

What are PowerApps and Flow? Microsoft PowerApps is a framework derived from Dynamics 365 (formerly Dynamics CRM) that allow you to build apps either with or without a form interface.  PowerApps works with Microsoft Flow.

Microsoft Flow is is a cloud software tool to build automated workflows that connect to many Microsoft and non-Microsoft systems and services.  For instance, you could write a workflow which would create a record in Dynamics 365 whenever a new file …