ROPC warnings

Author: Rick-Anderson

entity-framework/core/cli/powershell.md

@@ -11,6 +11,8 @@ The Package Manager Console (PMC) tools for Entity Framework Core perform design
 
 If you aren't using Visual Studio, we recommend the [EF Core Command-line Tools](xref:core/cli/dotnet) instead. The .NET Core CLI tools are cross-platform and run inside a command prompt.
 
+[!INCLUDE [managed-identities-test-non-production](~/core/includes/managed-identities-test-non-production.md)]
+
 ## Installing the tools
 
 Install the Package Manager Console tools by running the following command in **Package Manager Console**:
@@ -215,7 +217,7 @@ Parameters:
 
 | Parameter                                 | Description                                                                                                                                                                                                                                                                  |
 |:------------------------------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| <nobr>`-Connection <String>`</nobr>       | The connection string to the database. For ASP.NET Core 2.x projects, the value can be *name=\<name of connection string>*. In that case the name comes from the configuration sources that are set up for the project. This is a positional parameter and is required.      |
+| <nobr>`-Connection <String>`</nobr>       | The connection string to the database. The value can be *name=\<name of connection string>*. In that case the name comes from the configuration sources that are set up for the project. This is a positional parameter and is required.      |
 | <nobr>`-Provider <String>`</nobr>         | The provider to use. Typically this is the name of the NuGet package, for example: `Microsoft.EntityFrameworkCore.SqlServer`. This is a positional parameter and is required.                                                                                                |
 | <nobr>`-OutputDir <String>`</nobr>        | The directory to put entity class files in. Paths are relative to the project directory.                                                                                                                                                                                     |
 | <nobr>`-ContextDir <String>`</nobr>       | The directory to put the `DbContext` file in. Paths are relative to the project directory.                                                                                                                                                                                   |

entity-framework/core/managing-schemas/scaffolding/index.md

@@ -31,7 +31,6 @@ Both the PMC and the .NET CLI commands have two required arguments: the connecti
 
 The first argument to the command is a connection string to the database. The tools use this connection string to read the database schema.
 
-
 How the connection string is quoted and escaped depends on the shell is used to run the command. Refer to the shell's documentation. For example, PowerShell requires escaping `$`, but not `\`.
 
 The following example scaffolds entity types and a `DbContext` from the `Chinook` database located on the machine's SQL Server LocalDB instance, making use of the `Microsoft.EntityFrameworkCore.SqlServer` database provider.

entity-framework/core/miscellaneous/multitenancy.md

@@ -10,6 +10,8 @@ uid: core/miscellaneous/multitenancy
 
 Many line of business applications are designed to work with multiple customers. It is important to secure the data so that customer data isn't "leaked" or seen by other customers and potential competitors. These applications are classified as "multi-tenant" because each customer is considered a tenant of the application with their own set of data.
 
+[!INCLUDE [managed-identities-test-non-production](~/core/includes/managed-identities-test-non-production.md)]
+
 > [!IMPORTANT]
 > This document provides examples and solutions "as is." These are not intended to be "best practices" but rather "working practices" for your consideration.
 

entity-framework/ef6/fundamentals/configuring/config-file.md

@@ -6,7 +6,16 @@ ms.date: 10/23/2016
 uid: ef6/fundamentals/configuring/config-file
 ---
 # Configuration File Settings
-Entity Framework allows a number of settings to be specified from the configuration file. In general EF follows a ‘convention over configuration’ principle: all the settings discussed in this post have a default behavior, you only need to worry about changing the setting when the default no longer satisfies your requirements.  
+Entity Framework allows a number of settings to be specified from the configuration file. In general EF follows a ‘convention over configuration’ principle: all the settings discussed in this post have a default behavior, you only need to worry about changing the setting when the default no longer satisfies your requirements. 
+
+
+## Configuration data guidelines
+
+* Never store passwords or other sensitive data in configuration provider code or in plain text configuration files.
+* Don't use production secrets in development or test environments.
+* Specify secrets outside of the project so that they can't be accidentally committed to a source code repository.
+
+[!INCLUDE [managed-identities-test-non-production](~/core/includes/managed-identities-test-non-production.md)]
 
 ## A Code-Based Alternative  
 

entity-framework/ef6/fundamentals/configuring/connection-strings.md

@@ -11,10 +11,10 @@ This article covers how Entity Framework discovers which database connection to
 [!INCLUDE [managed-identities-test-non-production](~/core/includes/managed-identities-test-non-production.md)]
 
 
-Typically an Entity Framework application uses a class derived from DbContext. This derived class will call one of the constructors on the base DbContext class to control:  
+Typically an Entity Framework application uses a class derived from DbContext. This derived class calls one of the constructors on the base DbContext class to control:  
 
-- How the context will connect to a database — that is, how a connection string is found/used  
-- Whether the context will use calculate a model using Code First or load a model created with the EF Designer  
+- How the context connects to a database, that is, how a connection string is found and used  
+- Whether the context calculates a model using Code First or load a model created with the EF Designer  
 - Additional advanced options  
 
 The following fragments show some of the ways the DbContext constructors can be used.