Skip to content

Commit 930e130

Browse files
MikeRayMSFTMikeRayMSFT
committed
Merge branches 'main' and 'main' of https://github.com/MicrosoftDocs/sql-docs-pr into 20230712-arc-data-auto-enroll
2 parents c7310cf + 16c7714 commit 930e130

47 files changed

Lines changed: 962 additions & 522 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

‎azure-sql/database/database-copy.md‎

Lines changed: 8 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Create a transactionally consistent copy of an existing database in
44
author: WilliamDAssafMSFT
55
ms.author: wiassaf
66
ms.reviewer: mathoma
7-
ms.date: 12/19/2022
7+
ms.date: 7/12/2023
88
ms.service: sql-database
99
ms.subservice: data-movement
1010
ms.topic: how-to
@@ -212,17 +212,20 @@ To create a database copy, you will need to be in the following roles
212212

213213
- Subscription Owner or
214214
- SQL Server Contributor role or
215-
- Custom role on the source and target databases with following permission:
215+
- Custom role on the source server with following permissions:
216+
- Microsoft.Sql/servers/databases/read
217+
- Microsoft.Sql/servers/databases/write and
218+
- Custom role on the target server with following permissions:
219+
- Microsoft.Sql/servers/read
216220
- Microsoft.Sql/servers/databases/read
217221
- Microsoft.Sql/servers/databases/write
218222

219223
To cancel a database copy, you will need to be in the following roles
220224

221225
- Subscription Owner or
222226
- SQL Server Contributor role or
223-
- Custom role on the source and target databases with following permission:
224-
- Microsoft.Sql/servers/databases/read
225-
- Microsoft.Sql/servers/databases/write
227+
- Custom role on the target database with following permission:
228+
- Microsoft.Sql/servers/databases/delete
226229

227230
To manage database copy using the Azure portal, you will also need the following permissions:
228231

‎azure-sql/database/maintenance-window-configure.md‎

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -142,8 +142,7 @@ The following example creates a new managed instance and sets the maintenance wi
142142
-ResourceGroupName "your_resource_group_name" `
143143
-Location "your_mi_location" `
144144
-SubnetId /subscriptions/{SubID}/resourceGroups/{ResourceGroup}/providers/Microsoft.Network/virtualNetworks/{VNETName}/subnets/{SubnetName} `
145-
-MaintenanceConfigurationId "/subscriptions/{SubID}/providers/Microsoft.Maintenance/publicMaintenanceConfigurations/SQL_{Region}_{MaintenanceConfigName}" `
146-
-AsJob
145+
-MaintenanceConfigurationId "/subscriptions/{SubID}/providers/Microsoft.Maintenance/publicMaintenanceConfigurations/SQL_{Region}_{MaintenanceConfigName}"
147146
```
148147

149148
# [CLI](#tab/azure-cli)
@@ -322,8 +321,7 @@ It's important to make sure that the `$maintenanceConfig` value must be a valid
322321
```powershell-interactive
323322
Set-AzSqlInstance -Name "your_mi_name" `
324323
-ResourceGroupName "your_resource_group_name" `
325-
-MaintenanceConfigurationId "/subscriptions/{SubID}/providers/Microsoft.Maintenance/publicMaintenanceConfigurations/SQL_{Region}_{MaintenanceConfigName}" `
326-
-AsJob
324+
-MaintenanceConfigurationId "/subscriptions/{SubID}/providers/Microsoft.Maintenance/publicMaintenanceConfigurations/SQL_{Region}_{MaintenanceConfigName}"
327325
```
328326

329327
# [CLI](#tab/azure-cli)

‎azure-sql/database/threat-detection-configure.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -45,7 +45,7 @@ You can receive notifications about the detected threats via [email notification
4545

4646
## Set up Advanced Threat Protection using PowerShell
4747

48-
For a script example, see [Configure auditing and Advanced Threat Protection using PowerShell](/powershell/module/az.sql/get-azsqldatabaseadvancedthreatprotectionsetting?view=azps-10.0.0&preserve-view=true).
48+
For a script example, see [Configure auditing and Advanced Threat Protection using PowerShell](/powershell/module/az.sql/update-azsqlserveradvancedthreatprotectionsetting?preserve-view=true).
4949

5050
## Next steps
5151

‎azure-sql/managed-instance/backup-activity-monitor.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ Enterprise Audits may require proof of successful backups, time of backup, and d
2424

2525
## Query msdb database
2626

27-
To view backup activity, query the `msdb` database:
27+
To view backup activity, run the following query from user-defined database:
2828

2929
```sql
3030
SELECT TOP (30) bs.machine_name, bs.server_name, DB_NAME(DB_ID(bs.database_name)) AS [Database Name], bs.recovery_model,

‎azure-sql/managed-instance/november-2022-feature-wave-enroll.md‎

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ titleSuffix: Azure SQL Managed Instance
44
description: Learn how to enroll new and existing instances in the November 2022 feature wave.
55
author: MashaMSFT
66
ms.author: mathoma
7-
ms.date: 11/16/2022
7+
ms.date: 07/12/2023
88
ms.service: sql-managed-instance
99
ms.subservice: service-overview
1010
ms.topic: how-to
@@ -15,9 +15,9 @@ ms.topic: how-to
1515

1616
Learn how to enroll new and existing managed instances in the November 2022 feature wave for Azure SQL Managed Instance.
1717

18-
The November 2022 feature wave is rolling out over several months. The initial rollout phase focuses on managed instances that belong to Dev/Test subscription types. Other subscription types will enroll in upcoming months.
18+
The November 2022 feature wave is being released in a phased manner. The current phase makes managed instances belonging to Dev/Test subscriptions eligible for the feature wave.
1919

20-
Eligible existing instances that were created before November 2022 can enroll in the feature wave immediately to unlock new benefits and features.
20+
Existing eligible instances that were created before November 2022 can enroll in the feature wave immediately to unlock new benefits and features.
2121

2222
## New benefits and features
2323

@@ -26,7 +26,7 @@ The November 2022 feature wave introduced new features and automatic benefits fo
2626
The benefits in the feature wave include:
2727

2828
- **Fast instance provisioning**. It takes less time to deploy an instance.
29-
- [**Simplified connectivity architecture**](connectivity-architecture-overview.md). The connectivity architecture of SQL Managed Instance is simplified by removing the management endpoint and reducing the number of mandatory rules.
29+
- [**Improved network security**](connectivity-architecture-overview.md). Internal service traffic is now isolated and secured by Microsoft.
3030
- [**Enhanced virtual cluster**](connectivity-architecture-overview.md?tab=current#virtual-cluster-connectivity-architecture). The functionality of the underlying virtual cluster is enhanced.
3131

3232
These new preview features were introduced in the wave:
@@ -37,23 +37,23 @@ These new preview features were introduced in the wave:
3737

3838
For more information, see [Frequently asked questions](frequently-asked-questions-faq.yml#november-2022-feature-wave).
3939

40-
## Feature wave rollout
40+
## November 2022 feature wave rollout
4141

42-
The November 2022 feature wave is rolling out over several months. The initial rollout phase focuses on instances that belong to [Dev/Test subscriptions](frequently-asked-questions-faq.yml#what-azure-offers-and-subscription-types-are-enrolled-in-the-november-2022-feature-wave). Other subscription types will be enrolled in upcoming months. Unsupported subscription types can't be enabled individually.
42+
The November 2022 feature wave is being released in a phased manner. The current phase makes managed instances belonging to [Dev/Test subscriptions](frequently-asked-questions-faq.yml#what-azure-offers-and-subscription-types-are-enrolled-in-the-november-2022-feature-wave) eligible for the feature wave.
4343

4444
The enrollment experience is different for new instances and existing instances:
4545

4646
- *New instances* created after November 2022 in eligible subnets will be enrolled in the feature wave automatically and get access to the new benefits and features.
4747
- *Existing instances* will be enrolled in the November 2022 feature wave gradually and automatically. Eligible existing instances that were created before November 2022 can enroll in the feature wave immediately to unlock the new benefits and features.
4848

4949
> [!NOTE]
50-
> Benefits and features can't be enabled individually on instances that haven't enrolled in the feature wave.
50+
> Benefits and features can't be enabled individually on managed instances that haven't enrolled in the feature wave.
5151
5252
## Enroll an existing instance
5353

5454
Existing eligible instances that were created before November 2022 eventually will be automatically enrolled in the feature wave. However, you can choose to enroll your existing instance immediately if your instance meets the following conditions:
5555

56-
- Your instance is hosted in a subscription type that's ready for the November 2022 feature wave. Currently, only the Dev/Test subscription type is supported.
56+
- Your instance is hosted in a subscription type that's ready for the November 2022 feature wave. Currently, Dev/Test subscription type is supported.
5757
- You can update the virtual network subnet to one of the supported types:
5858

5959
- A new subnet
@@ -115,7 +115,7 @@ To confirm that your new instance is enrolled in the feature wave during deploym
115115

116116
1. Select **Review + Create** to validate your settings. Check the **Nov 2022 feature wave** section to confirm that all configuration options are compatible with the feature wave:
117117

118-
:::image type="content" source="media/november-2022-feature-wave-enroll/review-and-create.png" alt-text="Screenshot that shows the Review + create pane in the Azure portal, with the November 22 feature wave options highlighted.":::
118+
:::image type="content" source="media/november-2022-feature-wave-enroll/review-and-create.png" alt-text="Screenshot that shows the Review + create pane in the Azure portal, with the November 2022 feature wave options highlighted.":::
119119

120120
## Known issues
121121

‎azure-sql/managed-instance/public-endpoint-configure.md‎

Lines changed: 10 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: "Learn how to configure a public endpoint for Azure SQL Managed Ins
44
author: zoran-rilak-msft
55
ms.author: zoranrilak
66
ms.reviewer: vanto, mathoma
7-
ms.date: 06/12/2023
7+
ms.date: 07/14/2023
88
ms.service: sql-managed-instance
99
ms.subservice: security
1010
ms.topic: how-to
@@ -163,6 +163,15 @@ Use the Azure portal to allow public traffic within the network security group.
163163
> [!NOTE]
164164
> Port 3342 is used for public endpoint connections to managed instance, and can't be changed currently.
165165
166+
167+
## Confirm that routing is properly configured
168+
169+
A route with the 0.0.0.0/0 address prefix instructs Azure how to route traffic destined for an IP address that is not within the address prefix of any other route in a subnet's route table. When a subnet is created, Azure creates a default route to the 0.0.0.0/0 address prefix, with the **Internet** next hop type.
170+
171+
Overriding this default route without adding the necessary route(s) to ensure the public endpoint traffic is routed directly to **Internet** may cause asymmetric routing issues since incoming traffic does not flow via the Virtual appliance/Virtual network gateway. Ensure that all traffic reaching the managed instance over public internet goes back out over public internet as well by either adding specific routes for each source or setting the default route to the 0.0.0.0/0 address prefix back to **Internet** as next hop type.
172+
173+
See more the details about impact of changes on this default route at [0.0.0.0/0 address prefix](/azure/virtual-network/virtual-networks-udr-overview#default-route).
174+
166175
## Obtain the public endpoint connection string
167176

168177
1. Navigate to the managed instance configuration page that has been enabled for public endpoint. Select the **Connection strings** tab under the **Settings** configuration.

‎azure-sql/managed-instance/resource-limits.md‎

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -168,6 +168,9 @@ SQL Managed Instance currently supports deployment only on the following types o
168168
- [Enterprise Dev/Test](https://azure.microsoft.com/offers/ms-azr-0148p/)
169169
- [Pay-As-You-Go Dev/Test](https://azure.microsoft.com/offers/ms-azr-0023p/)
170170
- [Subscriptions with monthly Azure credit for Visual Studio subscribers](https://azure.microsoft.com/pricing/member-offers/credit-for-visual-studio-subscribers/)
171+
- [Free Trial](https://azure.microsoft.com/pricing/offers/ms-azr-0044p/)
172+
- [Azure For Students](https://azure.microsoft.com/pricing/offers/ms-azr-0170p/)
173+
- [Azure In Open](https://azure.microsoft.com/pricing/offers/ms-azr-0111p/)
171174

172175
## Regional resource limitations
173176

‎azure-sql/managed-instance/tde-certificate-migrate.md‎

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -154,6 +154,9 @@ If the certificate is kept in the SQL Server local machine certificate store, it
154154

155155
The certificate is now available to the specified managed instance, and the backup of the corresponding TDE-protected database can be restored successfully.
156156

157+
> [!NOTE]
158+
> Uploaded certificate is not visible in the sys.certificates catalog view. To confirm successful upload of the certificate you can run [RESTORE FILELISTONLY](/sql/t-sql/statements/restore-statements-filelistonly-transact-sql) command.
159+
157160
## Next steps
158161

159162
In this article, you learned how to migrate a certificate protecting the encryption key of a database with Transparent Data Encryption, from the on-premises or IaaS SQL Server instance to Azure SQL Managed Instance.

‎azure-sql/managed-instance/tempdb-configure.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -113,7 +113,7 @@ You can use SQL Server Management Studio (SSMS) to modify the growth increment o
113113
1. Right-click `tempdb`, and choose **Properties**.
114114
1. Select **Files** under **Select a page** to view the existing number of `tempdb` files.
115115
1. Choose the ellipses (...) next to a data file to open the **Change Autogrowth properties** dialog window.
116-
1. Check the box next to **Enable Autogrwoth** and then modify your autogrowth settings by specifying the file growth values, in either percent, or megabytes.
116+
1. Check the box next to **Enable Autogrowth** and then modify your autogrowth settings by specifying the file growth values, in either percent, or megabytes.
117117

118118
:::image type="content" source="media/tempdb-configure/change-growth-increment.png" alt-text="Screenshot of Change Autogrowth for tempdev in SSMS, with new database file name highlighted.":::
119119

‎azure-sql/managed-instance/timezones-overview.md‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Learn about the time zone specifics of Azure SQL Managed Instance
44
author: MladjoA
55
ms.author: mlandzic
66
ms.reviewer: mathoma
7-
ms.date: 10/19/2022
7+
ms.date: 07/13/2023
88
ms.service: sql-managed-instance
99
ms.subservice: service-overview
1010
ms.topic: reference
@@ -144,7 +144,7 @@ Using the same time zone across a primary and secondary instance in a failover g
144144
| UTC-02 | (UTC-02:00) Coordinated Universal Time-02 |
145145
| Mid-Atlantic Standard Time | (UTC-02:00) Mid-Atlantic - Old |
146146
| Azores Standard Time | (UTC-01:00) Azores |
147-
| Cabo Verde Standard Time | (UTC-01:00) Cabo Verde Is. |
147+
| Cape Verde Standard Time | (UTC-01:00) Cabo Verde Is. |
148148
| UTC | (UTC) Coordinated Universal Time |
149149
| GMT Standard Time | (UTC+00:00) Dublin, Edinburgh, Lisbon, London |
150150
| Greenwich Standard Time | (UTC+00:00) Monrovia, Reykjavik |
@@ -170,7 +170,7 @@ Using the same time zone across a primary and secondary instance in a failover g
170170
| Libya Standard Time | (UTC+02:00) Tripoli |
171171
| Namibia Standard Time | (UTC+02:00) Windhoek |
172172
| Arabic Standard Time | (UTC+03:00) Baghdad |
173-
| Türkiye Standard Time | (UTC+03:00) Istanbul |
173+
| Turkey Standard Time | (UTC+03:00) Istanbul |
174174
| Arab Standard Time | (UTC+03:00) Kuwait, Riyadh |
175175
| Belarus Standard Time | (UTC+03:00) Minsk |
176176
| Russian Standard Time | (UTC+03:00) Moscow, St. Petersburg |

0 commit comments

Comments
 (0)