Merge pull request #153915 from johnpapa/swa-config-file

changing file name to new name

Author: ShannonLeavitt

articles/static-web-apps/authentication-authorization.md

@@ -4,8 +4,8 @@ description: Learn to use different authorization providers to secure your stati
 services: static-web-apps
 author: craigshoemaker
 ms.service: static-web-apps
-ms.topic:  conceptual
-ms.date: 05/08/2020
+ms.topic: conceptual
+ms.date: 04/09/2021
 ms.author: cshoe
 ---
 
@@ -19,26 +19,26 @@ Azure Static Web Apps streamlines the authentication experience by managing auth
 - Google<sup>1</sup>
 - Twitter
 
-Provider-specific [invitations](#invitations) associate users with roles, and authorized users are granted access to [routes](routes.md) by rules defined in the _routes.json_ file.
+Provider-specific [invitations](#invitations) associate users with roles, and authorized users are granted access to [routes](routes.md) by rules defined in the _staticwebapp.config.json_ file.
 
 All authentication providers are enabled by default. To restrict an authentication provider, [block access](#block-an-authorization-provider) with a custom route rule.
 
 The topics of authentication and authorization significantly overlap with routing concepts. Make sure to read the [routing guide](routes.md) along with this article.
 
 ## Roles
 
-Every user who accesses a static web app belongs to one or more roles.  There are two built-in roles that users can belong to:
+Every user who accesses a static web app belongs to one or more roles. There are two built-in roles that users can belong to:
 
 - **anonymous**: All users automatically belong to the _anonymous_ role.
 - **authenticated**: All users who are logged in belong to the _authenticated_ role.
 
-Beyond the built-in roles, you can create new roles, assign them to users via invitations, and reference them in the _routes.json_ file.
+Beyond the built-in roles, you can create new roles, assign them to users via invitations, and reference them in the _staticwebapp.config.json_ file.
 
 ## Role management
 
 ### Add a user to a role
 
-To add users to your web site, you generate invitations which allow you to associate users to specific roles. Roles are defined and maintained in the _routes.json_ file.
+To add users to your web site, you generate invitations which allow you to associate users to specific roles. Roles are defined and maintained in the _staticwebapp.config.json_ file.
 
 <a name="invitations" id="invitations"></a>
 
@@ -48,25 +48,25 @@ Invitations are specific to individual authorization-providers, so consider the
 
 <a name="provider-user-details" id="provider-user-details"></a>
 
-| Authorization provider | Exposes a user's  |
-| ---------------------- | ----------------- |
-| Azure Active Directory | email address     |
-| Facebook               | email address     |
-| GitHub                 | username          |
-| Google<sup>1</sup>     | email address     |
-| Twitter                | username          |
+| Authorization provider | Exposes a user's |
+| ---------------------- | ---------------- |
+| Azure Active Directory | email address    |
+| Facebook               | email address    |
+| GitHub                 | username         |
+| Google<sup>1</sup>     | email address    |
+| Twitter                | username         |
 
 1. Navigate to a Static Web Apps resource in the [Azure portal](https://portal.azure.com).
 1. Under _Settings_, click on **Role Management**.
 1. Click on the **Invite** button.
 1. Select an _Authorization provider_ from the list of options.
 1. Add either the username or email address of the recipient in the _Invitee details_ box.
-    - For GitHub and Twitter, you enter the username. For all others, enter the recipient's email address.
+   - For GitHub and Twitter, you enter the username. For all others, enter the recipient's email address.
 1. Select the domain of your static site from the _Domain_ drop-down.
-    - The domain you select is the domain that appears in the invitation. If you have a custom domain associated with your site, you probably want to choose the custom domain.
+   - The domain you select is the domain that appears in the invitation. If you have a custom domain associated with your site, you probably want to choose the custom domain.
 1. Add a comma-separated list of role names in the _Role_ box.
 1. Enter the maximum number of hours you want the invitation to remain valid.
-    - The maximum possible limit is 168 hours, which is 7 days.
+   - The maximum possible limit is 168 hours, which is 7 days.
 1. Click the **Generate** button.
 1. Copy the link from the _Invite link_ box.
 1. Email the invitation link to the person you're granting access to your app.