1. Azure automation account
2. Microsoft PowerApps subscription
3. SharePoint List
4. SQL Azure Database

Snoozing an SAP system means the Azure VMs hosting that system are stopped and deallocated. Stopping VMs saves compute cost.

SAPSnooze PowerApps application provides the status of the SAP system and the VMs. It also provides a start button using which systems that are snoozed can be brought back online.

Following is the list of runbooks that’re needed:

1. ARSAPSnoozeGetSystemStatus.ps1 – Runbook to get status of SAP systems. This should be scheduled to run every 15 mins.
2. ARSAPSnoozeStartVM.ps1 – Runbook to start VMs. Once this runbook is created, create a webhook and capture the URL.

Hybrid worker group servers need to have the following modules installed: SharePointSDK Use command Install-Module SharePointSDK -Force to install

An automation run as account needs to be created that has permission to start the VMs

A SQL Azure table with the following structure needs to be created to capture usage statics of the PowerApps application. PowerApps would log the details each time a user logs in or start/stop/extend a system.

CREATE TABLE [dbo].[UserTelemetry]( [Timestamp] [datetime] NOT NULL, [Name] varchar NOT NULL, [Email] varchar NOT NULL, [System_SID] varchar NULL, [Action] varchar NULL, CONSTRAINT [PK_UserTelemetry] PRIMARY KEY CLUSTERED ( [Timestamp] ASC, [Name] ASC, [Email] ASC )WITH (STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF) ON [PRIMARY] ) ON [PRIMARY] GO

TimeStamp – Timestamp of the entry
Name – Name of the user
Email – Email address of the user A
Action – Action by the user (Login/Start/Stop/Extend)

A SharePoint list with the following columns needs to be created for maintain system information for PowerApps application.

1. Title – Title of the application. PowerApps application landing page will group the systems according to their application.
2. SID – SAP System ID
3. ResourceGroupName – Azure resource group that hosts the virtual machines for the SAP system
4. Status – Status of the SAP system. Allowed values are (Online, Offline, Unknown, Starting)
5. SAPStatus – Status of the SAP system
6. VMStatus – Status of virtual machines in Azure
7. User – Email address of the user who started the system
8. MESSAGESERVERHOST – Message server host name of the SAP system
9. MESSAGESERVERPORT – Message server port of the SAP system (36XX)
10. MESSAGESERVERHTTPPORT – Message server HTTP port of the SAP system (81XX)
11. GWSERV – Gateway port of the SAP system (33XX)

Fill the following details for the SAP system in the SharePoint list: Title, SID, ResourceGroupName, MESSAGESERVERHOST, MESSAGESERVERPORT, MESSAGESERVERHTTPPORT, GWSERV

Users who will be accessing the PowerApps application need edit access on the SharePoint list. This can be granted by an active directory security group. The active directory user that’s used by the Azure runbooks should have edit access on the SharePoint list.

1. Go to PowerApps Studio: https://preview.create.powerapps.com/studio/#
2. Create a new Connection for SharePoint.
3. Use the credentials of a user who has read and write permissions on the SharePoint List that you’ve created in the above step.
4. Create a new custom connector “Start SAP Systems” using the json file under /PowerApps/Start-SAP-Systems.swagger.json
5. Create the connection "Start SAP Systems" using the newly created custom connector
6. Create a new SQL Server Connection for collecting usage telemetry
7. Once the connectors are created, then import the PowerApps package from \PowerApps\SAPSnooze.zip by using the "Import canvas app" button to create the application
8. Click on the Action button to select the name of application and connectors and then click on import to finish importing the application.

Once created, edit the application in PowerApps studio, go to “Start” button function and update the web hook token that you’ve created in the step to setup Azure runbooks.
Similarly, update telemetry database table also, in the “Start” button function and in the App lan

Permission to PowerApps can be given to individual users or using active directory security groups. Please note people who’ve been access to PowerApps application should also be given edit access to the SharePoint list that’s created in the previous step.

Note:This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.