github/sql-server-samples
1
0
Fork 0
mirror of https://github.com/Microsoft/sql-server-samples.git synced 2025-12-08 14:58:54 +00:00
Code Issues Releases Wiki Activity

Merge pull request #896 from anosov1960/master

Browse Source 
Fixed minor errors
This commit is contained in:
Alexander (Sasha) Nosov
2021-02-04 11:36:36 -08:00
committed by GitHub
parent cc88456105 8abcdba142
commit a2e053e491
1 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
samples/manage/azure-hybrid-benefit/README.md
+5 -5
View File
@@ -100,7 +100,7 @@ $params =@{
# Running the script using Cloud Shell
Use the following steps to calculate the SQL Server license usage:
To run the script in the Cloud Shell, use the following steps:
1. Launch the [Cloud Shell](https://shell.azure.com/). For details, read [PowerShell in Cloud Shell](https://aka.ms/pscloudshell/docs).
@@ -128,7 +128,7 @@ You can track your license utilization over time by running this script on sched
```console
curl https://raw.githubusercontent.com/microsoft/sql-server-samples/master/samples/manage/azure-hybrid-benefit/sql-license-usage.ps1 -o sql-license-usage.ps1
```
2. [Create a new automation account](https://ms.portal.azure.com/#create/Microsoft.AutomationAccount) or use an existing one.
2. [Create a new automation account](https://ms.portal.azure.com/#create/Microsoft.AutomationAccount) or open an existing one.
1. Select *Rus as accounts* in the **Account Settings** group, open the automatically created *Azure Run As Account* and note or copy the Display Name property. You must add this user to all the subscriptions you wish to scan with the *Reader* access role. See [Role assignment portal](https://docs.microsoft.com/en-us/azure/role-based-access-control/role-assignments-portal) for the instructions about role assignments.
1. Select *Credentials* in the **Shared resources** group and create a credential object with the database username and password. The script will use these to connect to the specified database to save the license utilization data.
1. Select *Modules* in the **Shared resources** group and make sure your automation account have the following PowerShell modules installed. If not, add them from the Gallery.
@@ -139,14 +139,14 @@ curl https://raw.githubusercontent.com/microsoft/sql-server-samples/master/sampl
- Az.Sql
- Az.SqlVirtualMachine
1. Select *Runbooks* in the **Process automation** group and click on *Import a runbook*, select the file you downloaded in Step 1 and click **Create**.
1. When import is completed click on *Publish*.
1. When import is completed, click the *Publish* button.
1. From the runbook blade, click on the *Link to schedule* button and select an existing schedule or create a new one with the desired frequency of runs and the expiration time.
1. Click on *Parameters and run settings* and specify the following parameters:
- SUBID. Put in a subscription ID or leave it blank if you want to scan all the subscriptions the *Azure Run As Account* has been given access to in Step 3.
- SERVER. Put in the SQL Server connection endpoint (e.g. my-westus2-sql-server.database.windows.net)
- CRED. Put in the name of the credential object you created in Step 3.
- CRED. Put in the name of the credential object you created in Step 4.
- DATABASE. Put in the database name where you want to save the license utilization data.
- USEINRUNBOOKS. Select True to activate the logic that authenticates the runbook using the Run As account that was automatically created when you created your Automation account.
- USEINRUNBOOKS. Select True to activate the logic that authenticates the runbook using the *Azure Run As Account*.
1. Click **OK** to link to the schedule and **OK** again to create the job.
For more information about the runbooks, see the [Runbook tutorial](https://docs.microsoft.com/en-us/azure/automation/learn/automation-tutorial-runbook-textual-powershell)