Merging changes synced from https://github.com/MicrosoftDocs/sql-docs-pr (branch live)

Author: Learn Build Service GitHub App

azure-sql/managed-instance/winauth-azuread-overview.md

@@ -1,18 +1,19 @@
 ---
-title: What is Windows Authentication for Microsoft Entra principals on Azure SQL Managed Instance?
+title: What Is Windows Authentication for Microsoft Entra Principals on Azure SQL Managed Instance?
 titleSuffix: Azure SQL Managed Instance
 description: Learn about Windows Authentication for Microsoft Entra principals on Azure SQL Managed Instance.
 author: sravanisaluru
 ms.author: srsaluru
-ms.reviewer: mathoma, bonova, urmilano, wiassaf
-ms.date: 09/27/2023
+ms.reviewer: mathoma, bonova, urmilano, wiassaf, randolphwest
+ms.date: 04/17/2025
 ms.service: azure-sql-managed-instance
 ms.subservice: deployment-configuration
 ms.topic: overview
 ---
 
-# What is Windows Authentication for Microsoft Entra principals on Azure SQL Managed Instance? 
-[!INCLUDE[appliesto-sqlmi](../includes/appliesto-sqlmi.md)]
+# What is Windows Authentication for Microsoft Entra principals on Azure SQL Managed Instance?
+
+[!INCLUDE [appliesto-sqlmi](../includes/appliesto-sqlmi.md)]
 
 [Azure SQL Managed Instance](sql-managed-instance-paas-overview.md) is the intelligent, scalable cloud database service that combines the broadest SQL Server database engine compatibility with the benefits of a fully managed and evergreen platform as a service. Kerberos authentication for Microsoft Entra ID ([formerly Azure Active Directory](/entra/fundamentals/new-name)) enables Windows Authentication access to Azure SQL Managed Instance. Windows Authentication for managed instances empowers customers to move existing services to the cloud while maintaining a seamless user experience and provides the basis for infrastructure modernization.
 
@@ -24,7 +25,7 @@ As customers modernize their infrastructure, application, and data tiers, they a
 
 [!INCLUDE [entra-authentication-options](../includes/entra-authentication-options.md)]
 
-However, some legacy apps can't change their authentication to Microsoft Entra ID: legacy application code may longer be available, there may be a dependency on legacy drivers, clients may not be able to be changed, and so on. Windows Authentication for Microsoft Entra principals removes this migration blocker and provides support for a broader range of customer applications.
+However, some legacy apps can't change their authentication to Microsoft Entra ID: legacy application code might no longer be available, there could be a dependency on legacy drivers, clients might not be able to be changed, and so on. Windows Authentication for Microsoft Entra principals removes this migration blocker and provides support for a broader range of customer applications.
 
 Windows Authentication for Microsoft Entra principals on managed instances is available for devices or virtual machines (VMs) joined to Active Directory, Microsoft Entra ID, or hybrid Microsoft Entra ID - a hybrid Microsoft Entra user identity exists both in Microsoft Entra ID and Active Directory and can access a managed instance in Azure using Microsoft Entra Kerberos.
 
@@ -38,7 +39,6 @@ By enabling Windows Authentication for Microsoft Entra principals, customers can
 
 Windows Authentication for Microsoft Entra principals also enables the following patterns on managed instances. These patterns are frequently used in traditional on-premises SQL Servers:
 
-
 - **"Double hop" authentication**: Web applications use IIS identity impersonation to run queries against an instance in the security context of the end user.
 - **Traces using extended events and SQL Server Profiler** can be launched using Windows authentication, providing ease of use for database administrators and developers accustomed to this workflow. Learn how to [run a trace against Azure SQL Managed Instance using Windows Authentication for Microsoft Entra principals](winauth-azuread-run-trace-managed-instance.md).
 
@@ -48,9 +48,7 @@ Enabling Windows Authentication for Microsoft Entra principals on Azure SQL Mana
 
 For example, a customer can enable a mobile analyst, using proven tools that rely on Windows Authentication, to authenticate to a managed instance using biometric credentials. This can be accomplished even if the mobile analyst works from a laptop that is joined to Microsoft Entra ID.
 
-## Next steps
-
-Learn more about implementing Windows Authentication for Microsoft Entra principals on Azure SQL Managed Instance:
+## Related content
 
 - [How Windows Authentication for Azure SQL Managed Instance is implemented with Microsoft Entra ID and Kerberos](winauth-implementation-aad-kerberos.md)
 - [How to set up Windows Authentication for Azure SQL Managed Instance using Microsoft Entra ID and Kerberos](winauth-azuread-setup.md)

docs/database-engine/configure-windows/enable-or-disable-a-server-network-protocol.md

@@ -62,7 +62,7 @@ All network protocols are installed during installation, by [!INCLUDE[ssNoVersio
    You can run this script from any machine, with or without SQL Server installed. Make sure you have the **SqlServer** module installed.
 
    ```powershell
-   #requires the SqlServer module
+   # This script requires the SqlServer module
    Import-Module SQLServer
 
    $wmi = New-Object Microsoft.SqlServer.Management.Smo.Wmi.ManagedComputer <#computer_name#>
@@ -76,7 +76,7 @@ All network protocols are installed during installation, by [!INCLUDE[ssNoVersio
    $Tcp.IsEnabled = $true
    $Tcp.Alter()
    $Tcp
- 
+
    # Enable the named pipes protocol for the default instance.
    $uri = "ManagedComputer[@Name='<#computer_name#>']/ServerInstance[@Name='MSSQLSERVER']/ServerProtocol[@Name='Np']"
    $Np = $wmi.GetSmoObject($uri)
@@ -99,22 +99,31 @@ After you enable or disable protocols, you must stop and restart the [!INCLUDE[s
 
 ```powershell
 # Get a reference to the ManagedComputer class.
-CD SQLSERVER:\SQL\<computer_name>
+Set-Location SQLSERVER:\SQL\<computer_name>
 $Wmi = (get-item .).ManagedComputer
+
 # Get a reference to the default instance of the Database Engine.
 $DfltInstance = $Wmi.Services['MSSQLSERVER']
+
 # Display the state of the service.
 $DfltInstance
+
 # Stop the service.
 $DfltInstance.Stop();
+
 # Wait until the service has time to stop.
+
 # Refresh the cache.
 $DfltInstance.Refresh();
+
 # Display the state of the service.
 $DfltInstance
+
 # Start the service again.
 $DfltInstance.Start();
+
 # Wait until the service has time to start.
+
 # Refresh the cache and display the state of the service.
 $DfltInstance.Refresh();
 $DfltInstance

docs/reporting-services/install-windows/e-mail-settings-reporting-services-native-mode-configuration-manager.md

@@ -17,6 +17,9 @@ helpviewer_keywords:
 ---
 # Email settings in Reporting Services native mode (Report Server Configuration Manager)
 
+> [!IMPORTANT]
+> Exchange Online [announced](https://techcommunity.microsoft.com/blog/exchange/exchange-online-to-retire-basic-auth-for-client-submission-smtp-auth/4114750) the retirement of Basic Auth with Client Submission (SMTP AUTH) scheduled for September 2025. The Exchange Online team recommends three alternatives for customers who must continue to use Basic auth with Client Submission (SMTP AUTH): [High Volume Emails for Microsoft 365](/Exchange/mail-flow-best-practices/high-volume-mails-m365), [Azure Communication Services Email](/azure/communication-services/concepts/email/email-smtp-overview), or [Anonymous relay on Exchange servers](/exchange/mail-flow/connectors/allow-anonymous-relay). Customers currently using Exchange Online Basic Auth with Client Submission (SMTP AUTH) for email distribution through SSRS or PBIRS are advised to start switching to one of these alternatives based on their specific requirements.
+
 You can distribute reports through email by using the SQL Server Reporting Services (SSRS) email delivery extension. Depending on the email subscription configuration, distribution might include a notification, link, attachment, or embedded report. The email delivery extension works with your existing mail server technology that uses a Simple Mail Transfer Protocol (SMTP) server or forwarder. The report server connects to an SMTP server through Collaboration Data Objects (CDO) libraries (`cdosys.dll`) provided by the operating system.
 
 The report server email delivery extension isn't configured by default. You use the Report Server Configuration Manager to minimally configure the extension. To set advanced properties, edit the `RSReportServer.config` file. If you can't configure the report server to use this extension, you can deliver reports to a shared folder instead. For more information, see [File share delivery in Reporting Services](../../reporting-services/subscriptions/file-share-delivery-in-reporting-services.md).
@@ -42,7 +45,7 @@ Before you can use Report Server email delivery, you must set configuration valu
 > [!NOTE]
 > Report server email settings are based on CDO. For more information about specific settings, see the CDO production documentation.
 
-## <a name="rsconfigman"></a> Configure report server email by using the Report Server Configuration Manager
+## <a name="rsconfigman"></a>Configure report server email by using the Report Server Configuration Manager
 
 1. Start the Report Server Configuration Manager and connect to the report server instance.
 1. Go to **E-mail Settings**. 

docs/t-sql/statements/bulk-insert-transact-sql.md

@@ -4,7 +4,7 @@ description: Transact-SQL reference for the BULK INSERT statement.
 author: markingmyname
 ms.author: maghan
 ms.reviewer: randolphwest, wiassaf
-ms.date: 02/12/2025
+ms.date: 04/17/2025
 ms.service: sql
 ms.subservice: t-sql
 ms.topic: reference
@@ -28,7 +28,7 @@ monikerRange: "=azuresqldb-current || =azure-sqldw-latest || >=sql-server-2016 |
 ---
 # BULK INSERT (Transact-SQL)
 
-[!INCLUDE [SQL Server Azure SQL Database Azure SQL Managed Instance](../../includes/applies-to-version/sql-asdb-asdbmi.md)]
+[!INCLUDE [SQL Server Azure SQL Database Azure SQL Managed Instance](../../includes/applies-to-version/sql-asdb-asdbmi-fabricdw.md)]
 
 Imports a data file into a database table or view in a user-specified format in [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)].
 
@@ -91,9 +91,6 @@ The `BULK INSERT` statement has different arguments and options in different pla
 | Unsupported options | `*` wildcards in path | `*` wildcards in path | `DATA_SOURCE`, `FORMATFILE_DATA_SOURCE`, `ERRORFILE`, `ERRORFILE_DATA_SOURCE` |
 | Enabled options but without effect | | | `KEEPIDENTITY`, `FIRE_TRIGGERS`, `CHECK_CONSTRAINTS`, `TABLOCK`, `ORDER`, `ROWS_PER_BATCH`, `KILOBYTES_PER_BATCH`, and `BATCHSIZE` are not applicable. They will not throw a syntax error, but they will not have any effect | 
 
-> [!NOTE]
-> The BULK INSERT statement is in [preview in Fabric Data Warehouse](https://blog.fabric.microsoft.com/blog/bulk-insert-statement-in-fabric-datawarehouse).
-
 #### *database_name*
 
 The database name in which the specified table or view resides. If not specified, *database_name* is the current database.
@@ -135,9 +132,12 @@ Fabric Warehouse supports `*` wildcards that can match any character in the URI,
 
 ```sql
 BULK INSERT bing_covid_19_data
-FROM 'https://pandemicdatalake.blob.core.windows.net/public/curated/covid-19/bing_covid-19_data/latest/*.csv';
+FROM 'https://<data-lake>.blob.core.windows.net/public/curated/covid-19/bing_covid-19_data/latest/*.csv';
 ```
 
+> [!NOTE]  
+> Replace `<data-lake>.blob.core.windows.net` with an appropriate URL.
+
 #### BATCHSIZE = *batch_size*
 
 Specifies the number of rows in a batch. Each batch is copied to the server as one transaction. If this fails, [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] commits or rolls back the transaction for every batch. By default, all data in the specified data file is one batch. For information about performance considerations, see [Performance considerations](#performance-considerations) later in this article.
@@ -159,6 +159,15 @@ A situation in which you might want constraints disabled (the default behavior)
 
 Specifies the code page of the data in the data file. CODEPAGE is relevant only if the data contains **char**, **varchar**, or **text** columns with character values greater than **127** or less than **32**. For an example, see [Specify a code page](#d-specify-a-code-page).
 
+```sql
+BULK INSERT bing_covid_19_data
+FROM 'https://<data-lake>.blob.core.windows.net/public/curated/covid-19/bing_covid-19_data/latest/bing_covid-19_data.csv'
+WITH (CODEPAGE = '65001', FIRSTROW=2);
+```
+
+> [!NOTE]  
+> Replace `<data-lake>.blob.core.windows.net` with an appropriate URL.
+
 CODEPAGE isn't a supported option on Linux for [!INCLUDE [sssql17-md](../../includes/sssql17-md.md)]. For [!INCLUDE[sssql19-md](../../includes/sssql19-md.md)], only the **'RAW'** option is allowed for CODEPAGE.
 
 You should specify a collation name for each column in a [format file](../../relational-databases/import-export/use-a-format-file-to-bulk-import-data-sql-server.md).
@@ -174,6 +183,15 @@ You should specify a collation name for each column in a [format file](../../rel
 
 Specifies that BULK INSERT performs the import operation using the specified data-file type value.
 
+```sql
+BULK INSERT bing_covid_19_data
+FROM 'https://<data-lake>.blob.core.windows.net/public/curated/covid-19/bing_covid-19_data/latest/bing_covid-19_data.csv'
+WITH (DATAFILETYPE = 'char', FIRSTROW=2);
+```
+
+> [!NOTE]  
+> Replace `<data-lake>.blob.core.windows.net` with an appropriate URL.
+
 |DATAFILETYPE value|All data represented in:|
 |------------------------|------------------------------|
 |**char** (default)|Character format.<br /><br />For more information, see [Use Character Format to Import or Export Data &#40;SQL Server&#41;](../../relational-databases/import-export/use-character-format-to-import-or-export-data-sql-server.md).|
@@ -187,13 +205,16 @@ Specifies that BULK INSERT performs the import operation using the specified dat
 
 Specifies a named external data source pointing to the Azure Blob Storage location of the file that will be imported. The external data source must be created using the `TYPE = BLOB_STORAGE` option added in [!INCLUDE [sssql17-md](../../includes/sssql17-md.md)]. For more information, see [CREATE EXTERNAL DATA SOURCE](../../t-sql/statements/create-external-data-source-transact-sql.md). For an example, see [Import data from a file in Azure Blob Storage](#f-import-data-from-a-file-in-azure-blob-storage).
 
+> [!NOTE]  
+> Replace `<data-lake>.blob.core.windows.net` with an appropriate URL.
+
 ```sql
 CREATE EXTERNAL DATA SOURCE pandemicdatalake
-WITH (LOCATION='https://pandemicdatalake.blob.core.windows.net/public/',TYPE=BLOB_STORAGE)
+WITH (LOCATION='https://<data-lake>.blob.core.windows.net/public/',TYPE=BLOB_STORAGE)
 GO
 BULK INSERT bing_covid_19_data
 FROM 'curated/covid-19/bing_covid-19_data/latest/bing_covid-19_data.csv'
-WITH (DATA_SOURCE='pandemicdatalake',FIRSTROW = 2,LASTROW = 100,FIELDTERMINATOR = ',');
+WITH (DATA_SOURCE='<data-lake>',FIRSTROW = 2,LASTROW = 100,FIELDTERMINATOR = ',');
 ```
 
 #### ERRORFILE = '*error_file_path*'
@@ -214,6 +235,15 @@ Specifies a named external data source pointing to the Azure Blob Storage locati
 
 Specifies the number of the first row to load. The default is the first row in the specified data file. FIRSTROW is 1-based.
 
+```sql
+BULK INSERT bing_covid_19_data
+FROM 'https://<data-lake>.blob.core.windows.net/public/curated/covid-19/bing_covid-19_data/latest/bing_covid-19_data.csv'
+WITH (FIRSTROW=2);
+```
+
+> [!NOTE]  
+> Replace `<data-lake>.blob.core.windows.net` with an appropriate URL.
+
 The FIRSTROW attribute isn't intended to skip column headers. Skipping headers isn't supported by the BULK INSERT statement. If you choose to skip rows, the [!INCLUDE[ssDEnoversion](../../includes/ssdenoversion-md.md)] looks only at the field terminators, and doesn't validate the data in the fields of skipped rows.
 
 #### FIRE_TRIGGERS
@@ -305,6 +335,15 @@ Beginning with [!INCLUDE [sssql17-md](../../includes/sssql17-md.md)], and in Azu
 
 Specifies the field terminator to be used for **char** and **widechar** data files. The default field terminator is `\t` (tab character). For more information, see [Specify Field and Row Terminators &#40;SQL Server&#41;](../../relational-databases/import-export/specify-field-and-row-terminators-sql-server.md).
 
+```sql
+BULK INSERT bing_covid_19_data
+FROM 'https://<data-lake>.blob.core.windows.net/public/curated/covid-19/bing_covid-19_data/latest/bing_covid-19_data.csv'
+WITH (FIELDTERMINATOR = ',', FIRSTROW=2);
+```
+
+> [!NOTE]  
+> Replace `<data-lake>.blob.core.windows.net` with an appropriate URL.
+
 #### ROWTERMINATOR = '*row_terminator*'
 
 Specifies the row terminator to be used for **char** and **widechar** data files. The default row terminator is `\r\n` (newline character). For more information, see [Specify Field and Row Terminators &#40;SQL Server&#41;](../../relational-databases/import-export/specify-field-and-row-terminators-sql-server.md).