You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/URL-Shortener/Getting-Started.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
# Getting Started
2
2
3
-
Bicep is a domain-specific language that uses declarative syntax to deploy Azure resources.The bicep template (urlShortener.bicep) is found in the `./infrastructureTemplates` folder. To deploy the template, you will need the Entra ID Cloud Application Administrator role or higher.
3
+
Bicep is a domain-specific language that uses declarative syntax to deploy Azure resources.The bicep template (urlShortener.bicep) is found in the `./infrastructureTemplates` folder. To deploy the template, you will need the Entra ID Cloud Application Administrator role or higher.
4
4
5
5
## Steps
6
6
@@ -32,7 +32,7 @@ If you want to set this up on-prem or in a different environment, please refer t
32
32
33
33
It is pointed to the resource group name that was just created as well as the ARM resource that was just created. This will begin the deployment process.
34
34
35
-
6. Head over to your as portal at `https://portal.azure.com` and browse to Resource Group > Deployments. This will replicate your Deployment
35
+
6. Head over to your Azure portal at `https://portal.azure.com` and browse to Resource Group > Deployments. This will replicate your Deployment
36
36
37
37
7. The bicep template also creates an End User Login for the application. This is located at `https://entra.microsoft.com`. This will be under Entra ID > App Registrations on the left hand column.
38
38
@@ -72,7 +72,7 @@ If you want to set this up on-prem or in a different environment, please refer t
72
72
73
73
in your terminal and navigate to the `bin` folder and delete the `test` folder.
74
74
75
-
13. Using a file archiver of your choice, such as 7zip, select `bin` folder, `node_modules` folder, and the `package.json` folder, and drag it into your file archiver to create a .zip package that is Azure compatible.
75
+
13. Using a file archiver of your choice, such as 7zip, select `bin` folder, `node_modules` folder, and the `package.json` file, and drag it into your file archiver to create a .zip package that is Azure compatible.
76
76
The bin folder contains all of the URL shortener command and control logic.
77
77
The node modules contains all of the dependencies.
78
78
The package.json contains the package manifest, which is used to launch the application.
@@ -87,7 +87,7 @@ If you want to set this up on-prem or in a different environment, please refer t
87
87
88
88
Click `Y` to Confirm
89
89
90
-
15. Type `Microsoft.Sql/servers/azureADO` should now be created which means that the app is now single sign on admin of the system.
90
+
15. The resource of type `Microsoft.Sql/servers/azureADO` should now be created which means that the app is now single sign on admin of the system.
91
91
92
92
16. The azure app service should have the binaries able to run the application, which can be confirmed by going to the web app > going to Deployment Center > Logs > status should be Succeeded (Active)
93
93
@@ -101,7 +101,7 @@ If you want to set this up on-prem or in a different environment, please refer t
101
101
disconnect-AzAccount
102
102
```
103
103
104
-
to log out of Azure. Run `npm install` to get all your dependencies back since the migration script is technically a developer dependency. Next set an environment variable. This was done by left clicking on Powertoys and selecting Environment Variables, Underneath Default varaibles > User click on `Add variable`.
104
+
to log out of Azure. Run `npm install` to get all your dependencies back since the migration script is technically a developer dependency. Next set an environment variable. This was done by left clicking on Powertoys and selecting Environment Variables, Underneath Default variables > User click on `Add variable`.
0 commit comments