4/9/2025 PM Publish (#33782)

* [Azure SQL Database] Copilot GA release

* Fabric changes for sp-rename and ALTER TABLE articles

* [Azure SQL Database]  Copilot GA release

* made edits to the FAQ and removed some sample prompts

* remove erroneous file

* Moved the table of copilot prompts to a separate file and linked to it from the over view file

* move the note

* edit table file

* acrolinx improvement

* add description to prompt file

* Removed all references to preview

* edit best practices section

* fix broken link

* remove line 78

* add to tOC

* Update docs/t-sql/statements/alter-table-transact-sql.md

* update metadata

* edit intro paragraph and H1 title

* minor edits

* add migration tags

* minor edits

* add an additional link to related content area

* Learn Editor: Update create-view-transact-sql.md

* update Metadata

* Learn Editor: Update create-view-transact-sql.md

* Learn Editor: Update grant-object-permissions-transact-sql.md

* update Metadata

* Learn Editor: Update grant-object-permissions-transact-sql.md

* correct typos and add question back to FAQ

* [Azure SQL Database] more copilot edits

* acrolinx improvement

* acrolinx improvements

* some more branding changes and minor edits

* remove additional include file

* [Azure SQL Database] minor edits and updates

* Minor improvements

* Apply suggestions from code review

Co-authored-by: Chad Kittel <[email protected]>

* At-scale migration assessment for SQL Server enabled by Azure Arc

* Staging IO Analysis GA

* Update docs/t-sql/statements/grant-object-permissions-transact-sql.md

Co-authored-by: Van To <[email protected]>

* 20250409 schemabinding

* Confirm merge from FromPublicRepo to main to sync with https://github.com/MicrosoftDocs/sql-docs (branch live) (#33773)

* 4/8/2025 AM Publish (#33752)

* Fix include file and refresh associated articles

* [SCOPED] SQL Tools content: Update author, add ms.collection, fix metadata

* added edge case when the parameter is 0

* Edit pass

* Update sys-databases-transact-sql.md

* Merge pull request #33738 from MicrosoftDocs/release-azure-sql-copilot-ga

[Azure SQL Database] Azure SQL Database Copilot - Release branch to main 04/08/2025 @ 1030am PST

---------

Co-authored-by: Randolph West MSFT <[email protected]>
Co-authored-by: James Barnett <[email protected]>
Co-authored-by: YanoOfQueenscastle <[email protected]>
Co-authored-by: TWINKLE CYRIL <[email protected]>
Co-authored-by: prmerger-automator[bot] <40007230+prmerger-automator[bot]@users.noreply.github.com>
Co-authored-by: Mark Ghanayem <[email protected]>

* Added missing column in output table

Added the missing 'job_name' column in the output table.

---------

Co-authored-by: Bo wen Yang <[email protected]>
Co-authored-by: Randolph West MSFT <[email protected]>
Co-authored-by: James Barnett <[email protected]>
Co-authored-by: YanoOfQueenscastle <[email protected]>
Co-authored-by: TWINKLE CYRIL <[email protected]>
Co-authored-by: prmerger-automator[bot] <40007230+prmerger-automator[bot]@users.noreply.github.com>
Co-authored-by: Mark Ghanayem <[email protected]>
Co-authored-by: finnigd <[email protected]>

* correct conflict

* reworked the order

* Update docs/t-sql/statements/create-view-transact-sql.md

Co-authored-by: Mark Ghanayem <[email protected]>

* 20250409 1059 edit pass

* 20250409 edit pass acrolinx

* Updated steps for NSP (#33759)

* Updated steps for NSP

* Fixed image path

* review and remove sensitive info

* edit

* rename image resources

---------

Co-authored-by: VanMSFT <[email protected]>

---------

Co-authored-by: Mark Ghanayem <[email protected]>
Co-authored-by: Alma Jenks <[email protected]>
Co-authored-by: TWINKLE CYRIL <[email protected]>
Co-authored-by: Randolph West MSFT <[email protected]>
Co-authored-by: Jodi Martis <[email protected]>
Co-authored-by: James Barnett <[email protected]>
Co-authored-by: chroux <[email protected]>
Co-authored-by: Jovan Popovic (MSFT) <[email protected]>
Co-authored-by: Chad Kittel <[email protected]>
Co-authored-by: prmerger-automator[bot] <40007230+prmerger-automator[bot]@users.noreply.github.com>
Co-authored-by: Ajith Krishnan <[email protected]>
Co-authored-by: Masha MSFT <[email protected]>
Co-authored-by: Regan Downer <[email protected]>
Co-authored-by: William Assaf MSFT <[email protected]>
Co-authored-by: Van To <[email protected]>
Co-authored-by: learn-build-service-prod[bot] <113403604+learn-build-service-prod[bot]@users.noreply.github.com>
Co-authored-by: YanoOfQueenscastle <[email protected]>
Co-authored-by: finnigd <[email protected]>
Co-authored-by: Jill Grant <[email protected]>
Co-authored-by: sudhanshukhera <[email protected]>

Author: 21 people

azure-sql/copilot/copilot-azure-sql-faq.yml

@@ -25,10 +25,6 @@ sections:
           In Azure SQL Database, where can I find Microsoft Copilot in Azure?
         answer: |
           The Copilot capabilities in Azure SQL Database include Copilot in the Azure portal experience: [Azure Copilot integration](copilot-azure-sql-overview.md)
-      - question: |
-          How do I enable Microsoft Copilot in Azure for my Azure tenant?
-        answer: |
-          Review the steps in [Enable Microsoft Copilot in Azure for your Azure tenant](copilot-azure-sql-overview.md#enable-copilot-in-your-azure-tenant). Microsoft Copilot skills in Azure SQL Database are currently in preview for a limited number of early adopters. To sign up for this program, visit [Request Access to Copilot in Azure SQL Database: Preview](https://aka.ms/sqlcopilot-signup).
       - question: |
           How does Copilot use data from my Azure SQL Database environment?
         answer: |

azure-sql/copilot/copilot-azure-sql-overview.md

@@ -3,7 +3,7 @@ title: Microsoft Copilot in Azure with Azure SQL Database Overview
 description: "Learn more about the possibilities of Microsoft Copilot in Azure with Azure SQL Database for administrators and developers."
 author: markingmyname
 ms.author: maghan
-ms.reviewer: kendalv, jenhayes, wiassaf
+ms.reviewer: kendalv, jenhayes
 ms.date: 04/08/2025
 ms.service: azure-sql-database
 ms.subservice: sql-ai-copilot

azure-sql/database/doc-changes-updates-release-notes-whats-new.md

@@ -68,9 +68,10 @@ The following table lists features of Azure SQL Database that have been made gen
 
 | Feature | GA Month | Details |
 | --- | --- | --- |
+| **Copilot in Microsoft Azure with SQL Database** | April 2025 | [Copilot in Azure with Azure SQL Database](../copilot/copilot-azure-sql-overview.md) is a [capability](/azure/copilot/capabilities#perform-tasks) of the [Microsoft Copilot in Azure](/azure/copilot/overview) experience that enhances the management and operation of Azure services, providing robust capabilities for SQL-dependent applications. |
 | **Manually initiate cutover for conversion to Hyperscale** | April 2025 | When converting an Azure SQL Database to the Hyperscale service tier, you have a new [option to manually initiate the cutover](https://aka.ms/hs-conversion-v2-ga). For more information, see [Convert an existing database to Hyperscale](convert-to-hyperscale.md). |
 | **Availability metric**| February 2025 | Availability is presented as a metric in the Azure Monitor metrics. Driven by a variety of user connection failures, you can [monitor and configure alerts on Azure SQL Database Availability](monitoring-metrics-alerts.md#availability-metric). For more information, see [Blog: Availability metric is now generally available](https://techcommunity.microsoft.com/blog/azuresqlblog/availability-metric-for-azure-sql-db-is-now-generally-available/4379174).|
-| **sys.dm_database_backups** | February 2025 | The [sys.dm_database_backups](/sql/relational-databases/system-dynamic-management-views/sys-dm-database-backups-azure-sql-database?view=azuresqldb-current&preserve-view=true) DMV returns information about the [automated backups of a database](automated-backups-overview.md). | 
+| **sys.dm_database_backups** | February 2025 | The [sys.dm_database_backups](/sql/relational-databases/system-dynamic-management-views/sys-dm-database-backups-azure-sql-database?view=azuresqldb-current&preserve-view=true) DMV returns information about the [automated backups of a database](automated-backups-overview.md). |
 | **Free Azure SQL Database** | January 2025 | Use [Azure SQL Database for free](free-offer.md), for the life of your subscription. This free offer provides up to ten free General Purpose databases, each with 100,000 vCore seconds of compute, every month. For more information, see [Blog: General availability of Azure SQL Database free offer](https://aka.ms/azuresqlfreedb).|
 | **Hyperscale support for database and file shrink**  | January 2025 | [Database and file shrink commands](file-space-manage.md) are now generally available for Azure SQL Database Hyperscale. For more information, see the [Shrink in Hyperscale Generally Available blog post](https://aka.ms/hs-shrink-ga).|
 | **Fabric mirrored databases** | November 2024 | With [Fabric Mirroring](/fabric/database/mirrored-database/overview), you can [mirror databases in Azure SQL Database to Microsoft Fabric](/fabric/database/mirrored-database/overview). You can continuously replicate your existing data estate directly into Fabric's OneLake, including data from Azure SQL Database.|

azure-sql/database/media/network-security-perimeter/associate-sql-network-security-perimeter.png

@@ -5,7 +5,7 @@ description: Overview of Network Security Perimeter for Azure SQL Database
 author: VanMSFT
 ms.author: vanto
 ms.reviewer: wiassaf, vanto, mathoma
-ms.date: 11/19/2024
+ms.date: 04/09/2025
 ms.service: azure-sql-database
 ms.subservice: security
 ms.topic: how-to
@@ -20,15 +20,31 @@ Network Security Perimeter (preview) secures both inbound and outbound network t
 > [!IMPORTANT]  
 > - This article applies to both Azure SQL Database and [dedicated SQL pool (formerly SQL DW)](/azure/synapse-analytics/sql-data-warehouse/sql-data-warehouse-overview-what-is) in Azure Synapse Analytics. These settings apply to all SQL Database and dedicated SQL pool (formerly SQL DW) databases associated with the server. For simplicity, the term 'database' refers to both databases in Azure SQL Database and Azure Synapse Analytics. Likewise, any references to 'server' is referring to the [logical SQL server](logical-servers.md) that hosts Azure SQL Database and dedicated SQL pool (formerly SQL DW) in Azure Synapse Analytics. This article does *not* apply to Azure SQL Managed Instance or dedicated SQL pools in Azure Synapse Analytics workspaces.
 
-## Associate SQL Database with a Network Security Perimeter in the Azure portal
+## Getting Started
 
-1. Search for **Network Security Perimeter** in the Azure portal search bar and then select the **Create** button and create the resource.
-1. Provide a **Name** and **Region** and choose the subscription.
-1. Under the **Resources** section, select the **Associate** button and navigate to the SQL Database you want to add.
+1. In the Azure portal, search for **Network Security Perimeter** in the resource list and then select **Create**.
 
    :::image type="content" source="media/network-security-perimeter/associate-sql-network-security-perimeter.png" alt-text="Screenshot of creating a network security perimeter in the Azure portal.":::
 
-1. Go through the rest of the creation process without entering anything in **Inbound access rules** or **Outbound access rules**.
+1. Provide a **Name** and **Region** and choose the subscription.
+1. Under the **Resources** section, select the **Add** button and navigate to the SQL Database you want to associate with the perimeter.
+1. Add an Inbound access rule. The source type can be either an IP address, a subscription, or other network security perimeters.
+1. Add an Outbound access rule to allow resources inside the perimeter to connect to resources outside the perimeter
+
+If you already have an existing Azure SQL Database and are looking to add security perimeter, use the following steps:
+
+1. In the Azure portal, search for the existing Network Security Perimeter.
+1. Select **Associated Resources** from the **Settings** menu.
+1. Select the **Add** button and select **Associate resources with an existing profile**.
+
+   :::image type="content" source="media/network-security-perimeter/associated-resources-sql-network-security-perimeter.png" alt-text="Screenshot of associated resources for network security perimeter in the Azure portal.":::
+
+1. Select your **Profile** from the dropdown and select **Add**.
+
+   :::image type="content" source="media/network-security-perimeter/select-associated-resources-sql-network-security-perimeter.png" alt-text="Screenshot of adding an associated resource for network security perimeter in the Azure portal.":::
+
+1. **Search** for your SQL Database resource, **Select** the required resource, and select **Associate**.
+
 
 ## Using SQL Database with a Network Security Perimeter
 
@@ -41,6 +57,7 @@ Login failed because the network security perimeter denied inbound access.
 
 ## Related content
 
+- [What is a network security perimeter?](/azure/private-link/network-security-perimeter-concepts)
 - [Quickstart: Create a network security perimeter - Azure portal](/azure/private-link/create-network-security-perimeter-portal)
 - [Quickstart: Create a network security perimeter - Azure PowerShell](/azure/private-link/create-network-security-perimeter-powershell)
 - [Quickstart: Create a network security perimeter - Azure CLI](/azure/private-link/create-network-security-perimeter-cli)

azure-sql/database/media/network-security-perimeter/associated-resources-sql-network-security-perimeter.png

@@ -86,7 +86,7 @@ The type of object being renamed. *object_type* is **varchar(13)**, with a defau
 | `COLUMN` | A column to be renamed. |
 | `DATABASE` | A user-defined database. This object type is required when renaming a database. |
 | `INDEX` | A user-defined index. Renaming an index with statistics, also automatically renames the statistics. |
-| `OBJECT` | An item of a type tracked in [sys.objects](../system-catalog-views/sys-objects-transact-sql.md). For example, OBJECT could be used to rename objects including constraints (CHECK, FOREIGN KEY, PRIMARY/UNIQUE KEY), user tables, and rules. |
+| `OBJECT` | An item of a type tracked in [sys.objects](../system-catalog-views/sys-objects-transact-sql.md). For example, OBJECT could be used to rename objects including constraints (CHECK, FOREIGN KEY, PRIMARY/UNIQUE KEY), user tables, columns, stored procedures, inline table-valued functions, table-valued functions, and rules. |
 | `STATISTICS` | **Applies to**: [!INCLUDE [ssSQL11](../../includes/sssql11-md.md)] and later and [!INCLUDE [ssazure-sqldb](../../includes/ssazure-sqldb.md)].<br /><br />Statistics created explicitly by a user or created implicitly with an index. Renaming the statistics of an index automatically renames the index as well. |
 | `USERDATATYPE` | A [CLR user-defined type](../clr-integration-database-objects-user-defined-types/clr-user-defined-types.md) added by executing [CREATE TYPE](../../t-sql/statements/create-type-transact-sql.md) or [sp_addtype](sp-addtype-transact-sql.md). |
 
@@ -97,7 +97,7 @@ The type of object being renamed. *object_type* is **varchar(13)**, with a defau
 **Applies to**: [!INCLUDE [fabric](../../includes/fabric.md)]
 
 - In `sp_rename` for the [!INCLUDE [fabricdw](../../includes/fabric-dw.md)] in [!INCLUDE [fabric](../../includes/fabric.md)], `OBJECT` is the only supported value for *@objtype*.
-- In `sp_rename` for the [!INCLUDE [fabricse](../../includes/fabric-se.md)] in [!INCLUDE [fabric](../../includes/fabric.md)], `OBJECT` is the only supported value for *@objtype*. Tables can't be renamed.
+- In `sp_rename` for the [!INCLUDE [fabricse](../../includes/fabric-se.md)] in [!INCLUDE [fabric](../../includes/fabric.md)], `OBJECT` is the only supported value for *@objtype*. Tables and columns can't be renamed.
 
 ## Return code values
 

azure-sql/database/media/network-security-perimeter/select-associated-resources-sql-network-security-perimeter.png

@@ -438,7 +438,7 @@ ALTER TABLE { database_name.schema_name.table_name | schema_name.table_name | ta
 {
   ADD  { column_name <data_type> [COLLATE collation_name] [ <column_options> ] } [ ,...n ]
 | ADD { <column_constraint> FOR column_name} [ ,...n ]
-| DROP { [CONSTRAINT] constraint_name } [ ,...n ]
+| DROP { COLUMN column_name | [CONSTRAINT] constraint_name } [ ,...n ]
 }
 [ ; ]