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: articles/active-directory/develop/tutorial-v2-angular-auth-code.md
+9-9Lines changed: 9 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: "Tutorial: Create an Angular app that uses the Microsoft identity platfor
3
3
titleSuffix: Microsoft identity platform
4
4
description: In this tutorial, you build an Angular single-page app (SPA) using auth code flow that uses the Microsoft identity platform to sign in users and get an access token to call the Microsoft Graph API on their behalf.
5
5
services: active-directory
6
-
author: joarroyo
6
+
author: jo-arroyo
7
7
manager: CelesteDG
8
8
9
9
ms.service: active-directory
@@ -445,7 +445,7 @@ In order to render certain UI only for authenticated users, components have to s
445
445
1. Add the `MsalBroadcastService` to *src/app/app.component.ts* and subscribe to the `inProgress$` observable to check if interaction is complete and an account is signed in before rendering UI. Your code should now look like this:
446
446
447
447
```javascript
448
-
import { Component, OnInit } from '@angular/core';
448
+
import { Component, OnInit, OnDestroy } from '@angular/core';
449
449
import { MsalService, MsalBroadcastService } from '@azure/msal-angular';
450
450
import { InteractionStatus } from '@azure/msal-browser';
451
451
import { Subject } from 'rxjs';
@@ -456,7 +456,7 @@ In order to render certain UI only for authenticated users, components have to s
456
456
templateUrl: './app.component.html',
457
457
styleUrls: ['./app.component.css']
458
458
})
459
-
export class AppComponent implements OnInit {
459
+
export class AppComponent implements OnInit, OnDestroy {
460
460
title = 'msal-angular-tutorial';
461
461
isIframe = false;
462
462
loginDisplay = false;
@@ -649,7 +649,7 @@ MSAL Angular provides `MsalGuard`, a class you can use to protect routes and req
649
649
3. Adjust the login calls in*src/app/app.component.ts* to take the `authRequest` set in the guard configurations into account. Your code should now look like the following:
650
650
651
651
```javascript
652
-
import { Component, OnInit, Inject } from '@angular/core';
652
+
import { Component, OnInit, OnDestroy, Inject } from '@angular/core';
653
653
import { MsalService, MsalBroadcastService, MSAL_GUARD_CONFIG, MsalGuardConfiguration } from '@azure/msal-angular';
654
654
import { InteractionStatus, RedirectRequest } from '@azure/msal-browser';
655
655
import { Subject } from 'rxjs';
@@ -660,7 +660,7 @@ MSAL Angular provides `MsalGuard`, a class you can use to protect routes and req
660
660
templateUrl: './app.component.html',
661
661
styleUrls: ['./app.component.css']
662
662
})
663
-
export class AppComponent implements OnInit {
663
+
export class AppComponent implements OnInit, OnDestroy {
664
664
title = 'msal-angular-tutorial';
665
665
isIframe = false;
666
666
loginDisplay = false;
@@ -869,7 +869,7 @@ Update the code in *src/app/app.component.html* to conditionally display a `Logo
869
869
Update the code in *src/app/app.component.ts* to sign out a user using redirects:
870
870
871
871
```javascript
872
-
import { Component, OnInit, Inject } from '@angular/core';
872
+
import { Component, OnInit, OnDestroy, Inject } from '@angular/core';
873
873
import { MsalService, MsalBroadcastService, MSAL_GUARD_CONFIG, MsalGuardConfiguration } from '@azure/msal-angular';
874
874
import { InteractionStatus, RedirectRequest } from '@azure/msal-browser';
Copy file name to clipboardExpand all lines: articles/app-service/app-service-plan-manage.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,7 @@ An [Azure App Service plan](overview-hosting-plans.md) provides the resources th
15
15
## Create an App Service plan
16
16
17
17
> [!TIP]
18
-
> If you have an App Service Environment, see [Create an App Service plan in an App Service Environment](environment/app-service-web-how-to-create-a-web-app-in-an-ase.md#createplan).
18
+
> If you wan't to create a plan in an App Service Environment, you can select it in the **Region** and follow the rest of the steps as described below.
19
19
20
20
You can create an empty App Service plan, or you can create a plan as part of app creation.
Copy file name to clipboardExpand all lines: articles/app-service/environment/app-service-app-service-environment-control-inbound-traffic.md
+3-4Lines changed: 3 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,18 +1,18 @@
1
1
---
2
2
title: Control inbound traffic v1
3
3
description: Learn how to control inbound traffic to an App Service Environment. This doc is provided only for customers who use the legacy v1 ASE.
4
-
author: ccompy
4
+
author: madsd
5
5
6
6
ms.assetid: 4cc82439-8791-48a4-9485-de6d8e1d1a08
7
7
ms.topic: article
8
8
ms.date: 01/11/2017
9
-
ms.author: stefsch
9
+
ms.author: madsd
10
10
ms.custom: seodec18
11
11
12
12
---
13
13
# How To Control Inbound Traffic to an App Service Environment
14
14
## Overview
15
-
An App Service Environment can be created in **either** an Azure Resource Manager virtual network, **or** a classic deployment model [virtual network][virtualnetwork]. A new virtual network and new subnet can be defined at the time an App Service Environment is created. Instead, an App Service Environment can be created in a pre-existing virtual network and pre-existing subnet. As of June 2016, ASEs can also be deployed into virtual networks that use either public address ranges or RFC1918 address spaces (private addresses). For more information, see [How To Create an App Service Environment][HowToCreateAnAppServiceEnvironment].
15
+
An App Service Environment can be created in **either** an Azure Resource Manager virtual network, **or** a classic deployment model [virtual network][virtualnetwork]. A new virtual network and new subnet can be defined at the time an App Service Environment is created. Instead, an App Service Environment can be created in a pre-existing virtual network and pre-existing subnet. As of June 2016, ASEs can also be deployed into virtual networks that use either public address ranges or RFC1918 address spaces (private addresses). For more information, see [How to Create an ASEv1 from template](app-service-app-service-environment-create-ilb-ase-resourcemanager.md).
16
16
17
17
Always create an App Service Environment within a subnet. A subnet provides a network boundary that can be used to lock down inbound traffic behind upstream devices and services. This setup allows only specific upstream IP addresses to accept HTTP and HTTPS traffic.
18
18
@@ -127,7 +127,6 @@ For more information, see [Securely connecting to Backend resources from an App
0 commit comments