Service | Microsoft Docs article | Related commit history on GitHub | Change details |
---|---|---|---|
active-directory | Groups Create Rule | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/active-directory/enterprise-users/groups-create-rule.md | If the rule you entered isn't valid, an explanation of why the rule couldn't be ## Turn on or off welcome email -When a new Microsoft 365 group is created, a welcome email notification is sent the users who are added to the group. Later, if any attributes of a user or device change, all dynamic group rules in the organization are processed for membership changes. Users who are added then also receive the welcome notification. You can turn off this behavior in [Exchange PowerShell](/powershell/module/exchange/users-and-groups/Set-UnifiedGroup). +When a new Microsoft 365 group is created, a welcome email notification is sent the users who are added to the group. Later, if any attributes of a user or device(only in case of security groups) change, all dynamic group rules in the organization are processed for membership changes. Users who are added then also receive the welcome notification. You can turn off this behavior in [Exchange PowerShell](/powershell/module/exchange/users-and-groups/Set-UnifiedGroup). ## Check processing status for a rule |
active-directory | Facebook Work Accounts Provisioning Tutorial | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/active-directory/saas-apps/facebook-work-accounts-provisioning-tutorial.md | |
active-directory | Frankli Io Provisioning Tutorial | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/active-directory/saas-apps/frankli-io-provisioning-tutorial.md | ms.assetid: 936223d1-7ba5-4300-b05b-cbf78ee45d0e Last updated 12/16/2021 |
active-directory | Freshservice Provisioning Tutorial | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/active-directory/saas-apps/freshservice-provisioning-tutorial.md | |
active-directory | Getabstract Provisioning Tutorial | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/active-directory/saas-apps/getabstract-provisioning-tutorial.md | |
active-directory | Github Ae Provisioning Tutorial | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/active-directory/saas-apps/github-ae-provisioning-tutorial.md | |
active-directory | Github Enterprise Managed User Provisioning Tutorial | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/active-directory/saas-apps/github-enterprise-managed-user-provisioning-tutorial.md | |
active-directory | Global Relay Identity Sync Provisioning Tutorial | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/active-directory/saas-apps/global-relay-identity-sync-provisioning-tutorial.md | |
active-directory | Golinks Provisioning Tutorial | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/active-directory/saas-apps/golinks-provisioning-tutorial.md | |
active-directory | Grammarly Provisioning Tutorial | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/active-directory/saas-apps/grammarly-provisioning-tutorial.md | |
active-directory | Gtmhub Provisioning Tutorial | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/active-directory/saas-apps/gtmhub-provisioning-tutorial.md | |
active-directory | H5mag Provisioning Tutorial | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/active-directory/saas-apps/h5mag-provisioning-tutorial.md | |
active-directory | Invision Provisioning Tutorial | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/active-directory/saas-apps/invision-provisioning-tutorial.md | |
active-directory | Klaxoon Provisioning Tutorial | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/active-directory/saas-apps/klaxoon-provisioning-tutorial.md | |
active-directory | Klaxoon Saml Provisioning Tutorial | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/active-directory/saas-apps/klaxoon-saml-provisioning-tutorial.md | |
active-directory | Logicgate Provisioning Tutorial | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/active-directory/saas-apps/logicgate-provisioning-tutorial.md | |
active-directory | Logmein Provisioning Tutorial | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/active-directory/saas-apps/logmein-provisioning-tutorial.md | |
active-directory | Mondaycom Provisioning Tutorial | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/active-directory/saas-apps/mondaycom-provisioning-tutorial.md | |
active-directory | Mx3 Diagnostics Connector Provisioning Tutorial | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/active-directory/saas-apps/mx3-diagnostics-connector-provisioning-tutorial.md | |
active-directory | Myday Provision Tutorial | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/active-directory/saas-apps/myday-provision-tutorial.md | |
active-directory | Netpresenter Provisioning Tutorial | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/active-directory/saas-apps/netpresenter-provisioning-tutorial.md | |
active-directory | Open Text Directory Services Provisioning Tutorial | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/active-directory/saas-apps/open-text-directory-services-provisioning-tutorial.md | |
active-directory | Playvox Provisioning Tutorial | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/active-directory/saas-apps/playvox-provisioning-tutorial.md | |
active-directory | Printer Logic Saas Provisioning Tutorial | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/active-directory/saas-apps/printer-logic-saas-provisioning-tutorial.md | |
active-directory | Proware Provisioning Tutorial | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/active-directory/saas-apps/proware-provisioning-tutorial.md | |
active-directory | Sap Analytics Cloud Provisioning Tutorial | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/active-directory/saas-apps/sap-analytics-cloud-provisioning-tutorial.md | |
active-directory | Secure Deliver Provisioning Tutorial | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/active-directory/saas-apps/secure-deliver-provisioning-tutorial.md | |
active-directory | Secure Login Provisioning Tutorial | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/active-directory/saas-apps/secure-login-provisioning-tutorial.md | |
active-directory | Segment Provisioning Tutorial | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/active-directory/saas-apps/segment-provisioning-tutorial.md | |
active-directory | Shopify Plus Provisioning Tutorial | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/active-directory/saas-apps/shopify-plus-provisioning-tutorial.md | |
active-directory | Sigma Computing Provisioning Tutorial | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/active-directory/saas-apps/sigma-computing-provisioning-tutorial.md | |
active-directory | Smallstep Ssh Provisioning Tutorial | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/active-directory/saas-apps/smallstep-ssh-provisioning-tutorial.md | |
active-directory | Splashtop Provisioning Tutorial | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/active-directory/saas-apps/splashtop-provisioning-tutorial.md | |
active-directory | Talentech Provisioning Tutorial | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/active-directory/saas-apps/talentech-provisioning-tutorial.md | |
active-directory | Thrive Lxp Provisioning Tutorial | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/active-directory/saas-apps/thrive-lxp-provisioning-tutorial.md | |
active-directory | Tic Tac Mobile Provisioning Tutorial | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/active-directory/saas-apps/tic-tac-mobile-provisioning-tutorial.md | |
active-directory | Travelperk Provisioning Tutorial | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/active-directory/saas-apps/travelperk-provisioning-tutorial.md | |
active-directory | Twingate Provisioning Tutorial | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/active-directory/saas-apps/twingate-provisioning-tutorial.md | |
active-directory | Visibly Provisioning Tutorial | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/active-directory/saas-apps/visibly-provisioning-tutorial.md | |
active-directory | Webroot Security Awareness Training Provisioning Tutorial | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/active-directory/saas-apps/webroot-security-awareness-training-provisioning-tutorial.md | |
api-management | Howto Protect Backend Frontend Azure Ad B2c | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/api-management/howto-protect-backend-frontend-azure-ad-b2c.md | editor: '' na Last updated 02/18/2021 |
app-service | Tutorial Java Spring Cosmosdb | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/app-service/tutorial-java-spring-cosmosdb.md | Open the `pom.xml` file in the `initial/spring-boot-todo` directory and add the <plugin> <groupId>com.microsoft.azure</groupId> <artifactId>azure-webapp-maven-plugin</artifactId>- <version>2.0.0</version> + <version>2.2.3</version> <configuration> <schemaVersion>v2</schemaVersion> bash-3.2$ mvn azure-webapp:deploy [INFO] Building spring-todo-app 2.0-SNAPSHOT [INFO] [INFO] -[INFO] azure-webapp-maven-plugin:2.0.0:deploy (default-cli) @ spring-todo-app +[INFO] azure-webapp-maven-plugin:2.2.3:deploy (default-cli) @ spring-todo-app Auth Type: AZURE_CLI Default subscription: xxxxxxxxx Username: xxxxxxxxx |
application-gateway | Create Gateway Internal Load Balancer App Service Environment | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/application-gateway/create-gateway-internal-load-balancer-app-service-environment.md | editor: '' tags: '' na |
azure-government | Documentation Accelerate Compliance | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/azure-government/compliance/documentation-accelerate-compliance.md | |
azure-government | Documentation Government Ase Disa Cap | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/azure-government/documentation-government-ase-disa-cap.md | cloud: gov documentationcenter: '' na |
azure-government | Documentation Government Cognitiveservices | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/azure-government/documentation-government-cognitiveservices.md | cloud: gov documentationcenter: '' na |
azure-government | Documentation Government Concept Naming Resources | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/azure-government/documentation-government-concept-naming-resources.md | description: Guidance on how customers should consider naming their Azure resour cloud: gov na |
azure-government | Documentation Government Connect Vs | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/azure-government/documentation-government-connect-vs.md | |
azure-government | Documentation Government Csp Application | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/azure-government/documentation-government-csp-application.md | cloud: gov documentationcenter: '' na |
azure-government | Documentation Government Developer Guide | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/azure-government/documentation-government-developer-guide.md | documentationcenter: '' na |
azure-government | Documentation Government Extension | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/azure-government/documentation-government-extension.md | cloud: gov documentationcenter: '' na |
azure-government | Documentation Government Get Started Connect With Cli | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/azure-government/documentation-government-get-started-connect-with-cli.md | |
azure-government | Documentation Government Get Started Connect With Portal | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/azure-government/documentation-government-get-started-connect-with-portal.md | |
azure-government | Documentation Government Howto Deploy Webandmobile | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/azure-government/documentation-government-howto-deploy-webandmobile.md | cloud: gov documentationcenter: '' na |
azure-government | Documentation Government Image Gallery | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/azure-government/documentation-government-image-gallery.md | cloud: gov documentationcenter: '' na |
azure-government | Documentation Government Manage Marketplace Partners | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/azure-government/documentation-government-manage-marketplace-partners.md | cloud: gov documentationcenter: '' na |
azure-government | Documentation Government Manage Oms | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/azure-government/documentation-government-manage-oms.md | cloud: gov documentationcenter: '' na |
azure-government | Documentation Government Overview Dod | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/azure-government/documentation-government-overview-dod.md | documentationcenter: '' na |
azure-government | Documentation Government Overview Jps | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/azure-government/documentation-government-overview-jps.md | documentationcenter: '' ms.assetid: ef582573-b6d6-4f74-8dcc-d31b2807ff24 na |
azure-government | Documentation Government Overview | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/azure-government/documentation-government-overview.md | documentationcenter: '' ms.assetid: 56d84e26-947e-4f3b-8e33-18247f1c7944 na |
azure-government | Documentation Government Plan Compliance | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/azure-government/documentation-government-plan-compliance.md | documentationcenter: '' ms.assetid: 1d2e0938-482f-4f43-bdf6-0a5da2e9a185 na |
azure-government | Documentation Government Plan Identity | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/azure-government/documentation-government-plan-identity.md | cloud: gov documentationcenter: '' na |
azure-government | Documentation Government Quickstarts Vm | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/azure-government/documentation-government-quickstarts-vm.md | cloud: gov documentationcenter: '' na |
azure-netapp-files | Application Volume Group Add Hosts | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/azure-netapp-files/application-volume-group-add-hosts.md | ms.assetid: na Last updated 11/19/2021 |
azure-netapp-files | Application Volume Group Add Volume Secondary | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/azure-netapp-files/application-volume-group-add-volume-secondary.md | ms.assetid: na Last updated 11/19/2021 |
azure-netapp-files | Application Volume Group Considerations | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/azure-netapp-files/application-volume-group-considerations.md | ms.assetid: na Last updated 11/19/2021 |
azure-netapp-files | Application Volume Group Delete | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/azure-netapp-files/application-volume-group-delete.md | ms.assetid: na Last updated 11/19/2021 |
azure-netapp-files | Application Volume Group Deploy First Host | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/azure-netapp-files/application-volume-group-deploy-first-host.md | ms.assetid: na Last updated 11/19/2021 |
azure-netapp-files | Application Volume Group Disaster Recovery | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/azure-netapp-files/application-volume-group-disaster-recovery.md | ms.assetid: na Last updated 12/22/2021 |
azure-netapp-files | Application Volume Group Introduction | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/azure-netapp-files/application-volume-group-introduction.md | ms.assetid: na Last updated 11/19/2021 |
azure-netapp-files | Application Volume Group Manage Volumes | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/azure-netapp-files/application-volume-group-manage-volumes.md | ms.assetid: na Last updated 11/19/2021 |
azure-netapp-files | Azacsnap Cmd Ref Backup | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/azure-netapp-files/azacsnap-cmd-ref-backup.md | ms.assetid: na Last updated 04/21/2021 |
azure-netapp-files | Azacsnap Cmd Ref Configure | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/azure-netapp-files/azacsnap-cmd-ref-configure.md | ms.assetid: na Last updated 04/21/2021 |
azure-netapp-files | Azacsnap Cmd Ref Delete | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/azure-netapp-files/azacsnap-cmd-ref-delete.md | ms.assetid: na Last updated 04/21/2021 |
azure-netapp-files | Azacsnap Cmd Ref Details | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/azure-netapp-files/azacsnap-cmd-ref-details.md | ms.assetid: na Last updated 04/21/2021 |
azure-netapp-files | Azacsnap Cmd Ref Restore | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/azure-netapp-files/azacsnap-cmd-ref-restore.md | ms.assetid: na Last updated 04/21/2021 |
azure-netapp-files | Azacsnap Cmd Ref Test | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/azure-netapp-files/azacsnap-cmd-ref-test.md | ms.assetid: na Last updated 08/04/2021 |
azure-netapp-files | Azacsnap Disaster Recovery | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/azure-netapp-files/azacsnap-disaster-recovery.md | ms.assetid: na Last updated 04/21/2021 |
azure-netapp-files | Azacsnap Get Started | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/azure-netapp-files/azacsnap-get-started.md | ms.assetid: na Last updated 04/21/2021 |
azure-netapp-files | Azacsnap Installation | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/azure-netapp-files/azacsnap-installation.md | ms.assetid: na Last updated 09/08/2021 |
azure-netapp-files | Azacsnap Introduction | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/azure-netapp-files/azacsnap-introduction.md | ms.assetid: na Last updated 04/21/2021 |
azure-netapp-files | Azacsnap Release Notes | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/azure-netapp-files/azacsnap-release-notes.md | ms.assetid: na Last updated 05/27/2021 |
azure-netapp-files | Azacsnap Tips | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/azure-netapp-files/azacsnap-tips.md | ms.assetid: na Last updated 08/04/2021 |
azure-netapp-files | Azacsnap Troubleshoot | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/azure-netapp-files/azacsnap-troubleshoot.md | ms.assetid: na Last updated 05/17/2021 |
azure-netapp-files | Azure Government | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/azure-netapp-files/azure-government.md | ms.assetid: na Last updated 10/14/2021 |
azure-netapp-files | Azure Netapp Files Configure Nfsv41 Domain | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/azure-netapp-files/azure-netapp-files-configure-nfsv41-domain.md | ms.assetid: na Last updated 11/11/2021 |
azure-netapp-files | Azure Netapp Files Cost Model | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/azure-netapp-files/azure-netapp-files-cost-model.md | ms.assetid: na Last updated 11/08/2021 |
azure-netapp-files | Azure Netapp Files Create Netapp Account | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/azure-netapp-files/azure-netapp-files-create-netapp-account.md | ms.assetid: na Last updated 10/04/2021 |
azure-netapp-files | Azure Netapp Files Create Volumes Smb | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/azure-netapp-files/azure-netapp-files-create-volumes-smb.md | ms.assetid: na Last updated 12/09/2021 |
azure-netapp-files | Azure Netapp Files Create Volumes | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/azure-netapp-files/azure-netapp-files-create-volumes.md | ms.assetid: na Last updated 10/04/2021 |
azure-netapp-files | Azure Netapp Files Delegate Subnet | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/azure-netapp-files/azure-netapp-files-delegate-subnet.md | ms.assetid: na Last updated 08/25/2021 |
azure-netapp-files | Azure Netapp Files Develop With Rest Api | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/azure-netapp-files/azure-netapp-files-develop-with-rest-api.md | ms.assetid: na Last updated 06/29/2021 |
azure-netapp-files | Azure Netapp Files Introduction | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/azure-netapp-files/azure-netapp-files-introduction.md | ms.assetid: na Last updated 10/04/2021 |
azure-netapp-files | Azure Netapp Files Manage Snapshots | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/azure-netapp-files/azure-netapp-files-manage-snapshots.md | ms.assetid: na Last updated 10/25/2021 |
azure-netapp-files | Azure Netapp Files Metrics | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/azure-netapp-files/azure-netapp-files-metrics.md | ms.assetid: na Last updated 09/29/2021 |
azure-netapp-files | Azure Netapp Files Network Topologies | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/azure-netapp-files/azure-netapp-files-network-topologies.md | ms.assetid: na Last updated 12/07/2021 |
azure-netapp-files | Azure Netapp Files Performance Considerations | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/azure-netapp-files/azure-netapp-files-performance-considerations.md | ms.assetid: na Last updated 02/19/2021 |
azure-netapp-files | Azure Netapp Files Register | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/azure-netapp-files/azure-netapp-files-register.md | ms.assetid: na Last updated 10/04/2021 |
azure-netapp-files | Azure Netapp Files Resize Capacity Pools Or Volumes | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/azure-netapp-files/azure-netapp-files-resize-capacity-pools-or-volumes.md | ms.assetid: na Last updated 04/30/2021 |
azure-netapp-files | Azure Netapp Files Resource Limits | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/azure-netapp-files/azure-netapp-files-resource-limits.md | ms.assetid: na Last updated 11/09/2021 |
azure-netapp-files | Azure Netapp Files Sdk Cli | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/azure-netapp-files/azure-netapp-files-sdk-cli.md | ms.assetid: na Last updated 10/21/2020 |
azure-netapp-files | Azure Netapp Files Service Levels | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/azure-netapp-files/azure-netapp-files-service-levels.md | ms.assetid: na Last updated 10/12/2020 |
data-factory | Managed Virtual Network Private Endpoint | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/data-factory/managed-virtual-network-private-endpoint.md | New-AzResource -ApiVersion "${apiVersion}" -ResourceId "${integrationRuntimeReso The following data sources have native Private Endpoint support and can be connected through private link from ADF Managed Virtual Network. - Azure Blob Storage (not including Storage account V1) - Azure Cognitive Search+- Azure Cosmos DB MongoDB API - Azure Cosmos DB SQL API - Azure Data Lake Storage Gen2 - Azure Database for MariaDB |
data-factory | Quickstart Create Data Factory Dot Net | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/data-factory/quickstart-create-data-factory-dot-net.md | Next, create a C# .NET console application in Visual Studio: ```powershell Install-Package Microsoft.Azure.Management.DataFactory Install-Package Microsoft.Azure.Management.ResourceManager -IncludePrerelease- Install-Package Microsoft.IdentityModel.Clients.ActiveDirectory + Install-Package Microsoft.Identity.Client ``` ## Create a data factory client Next, create a C# .NET console application in Visual Studio: using Microsoft.Azure.Management.ResourceManager; using Microsoft.Azure.Management.DataFactory; using Microsoft.Azure.Management.DataFactory.Models;- using Microsoft.IdentityModel.Clients.ActiveDirectory; + using Microsoft.Identity.Client; ``` 2. Add the following code to the **Main** method that sets the variables. Replace the placeholders with your own values. For a list of Azure regions in which Data Factory is currently available, select the regions that interest you on the following page, and then expand **Analytics** to locate **Data Factory**: [Products available by region](https://azure.microsoft.com/global-infrastructure/services/). The data stores (Azure Storage, Azure SQL Database, and more) and computes (HDInsight and others) used by data factory can be in other regions. Next, create a C# .NET console application in Visual Studio: ```csharp // Authenticate and create a data factory management client- var context = new AuthenticationContext("https://login.microsoftonline.com/" + tenantID); - ClientCredential cc = new ClientCredential(applicationId, authenticationKey); - AuthenticationResult result = context.AcquireTokenAsync( - "https://management.azure.com/", cc).Result; + IConfidentialClientApplication app = ConfidentialClientApplicationBuilder.Create(applicationId) + .WithAuthority("https://login.microsoftonline.com/" + tenantID) + .WithClientSecret(authenticationKey) + .WithLegacyCacheCompatibility(false) + .WithCacheOptions(CacheOptions.EnableSharedCacheOptions) + .Build(); ++ AuthenticationResult result = await app.AcquireTokenForClient( + new string[]{ "https://management.azure.com//.default"}) + .ExecuteAsync(); ServiceClientCredentials cred = new TokenCredentials(result.AccessToken); var client = new DataFactoryManagementClient(cred) { SubscriptionId = subscriptionId }; |
data-factory | Tutorial Enable Remote Access Intranet Tls Ssl Certificate | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/data-factory/tutorial-enable-remote-access-intranet-tls-ssl-certificate.md | + + Title: Enable remote access from intranet with TLS/SSL certificate (Advanced) +description: This tutorial provides steps for setting up a self-hosted integration runtime with multiple on-premises machines and enabling remote access from intranet with TLS/SSL certificate (Advanced) to secure communication between integration runtime nodes. +++++ Last updated : 12/21/2021+++# Enable remote access from intranet with TLS/SSL certificate (Advanced) ++In this tutorial, you will learn how to set up a self-hosted integration runtime with multiple on-premises machines and enable remote access from intranet with TLS/SSL certificate (Advanced) to secure communication between integration runtime nodes. ++## Prerequisites ++- An introduction to [SSL/TLS Strong Encryption](https://httpd.apache.org/docs/2.0/ssl/ssl_intro.html). +- Certificate could be a general TLS certificate for a Web Server. Requirements: + - The certificate must be a publicly trusted X509 v3 certificate. We recommend that you use certificates that are issued by a public partner certification authority (CA). + - Each integration runtime node must trust this certificate. + - We recommend Subject Alternative Name (SAN) certificates because all the fully qualified domain names (FQDN) of integration runtime nodes are required to be secured by this certificate. (WCF TLS/SSL validate only check last DNS Name in SAN was fixed in .NET Framework 4.6.1. Refer to [Mitigation: X509CertificateClaimSet.FindClaims Method](/dotnet/framework/migration-guide/mitigation-x509certificateclaimset-findclaims-method?redirectedfrom=MSDN) for more information.) + - Wildcard certificates (*) are not supported. + - The certificate must have a private key (like PFX format). + - The certificate can use any key size supported by Windows Server 2012 R2 for TLS/SSL certificates. + - We only support CSP (Cryptographic Service Provider) certificate so far. Certificates that use CNG keys (Key Storage Provider) aren't supported. ++## Steps ++1. Run below PowerShell command on all machines to get their FQDNs: ++ ```Powershell + [System.Net.Dns]::GetHostByName("localhost").HostName + ``` + For example, the FQDNs are **node1.domain.contoso.com** and **node2.domain.contoso.com**. ++2. Generate a certificate with the FQDNs of all machines in Subject Alternative Name. ++ :::image type="content" source="./media/tutorial-enable-remote-access-intranet-tls-ssl-certificate/generate-certificate-subject-alternative-name.png" alt-text="Screenshot that shows generating certificate in subject alternative name."::: + +3. Install the certificate on all nodes to **Local Machine** -> **Personal** so that it can be selected on the integration runtime configuration + 1. Click on the certificate and install it. + 1. Select **Local Machine** and enter the password. + + :::image type="content" source="./media/tutorial-enable-remote-access-intranet-tls-ssl-certificate/select-local-machine.png" alt-text="Screenshot that shows selecting local machine."::: ++ 1. Select **Place all certificates in the following store**. Click **Browse**. Select **Personal**. + 1. Select **Finish** to install the certificate. ++4. Enable remote access from intranet: + 1. During the self-hosted integration runtime node registration: + 1. Select **Enable remote access from intranet** and select **Next**. + + :::image type="content" source="./media/tutorial-enable-remote-access-intranet-tls-ssl-certificate/enable-remote-access-intranet.png" alt-text="Screenshot that shows enabling remote access from intranet."::: ++ 1. Set the **Tcp Port** (8060 by default). Make sure the port is open on firewall. + 1. Click **Select**. In the pop-up window, choose the right certificate and select **Finish**. + + :::image type="content" source="./media/tutorial-enable-remote-access-intranet-tls-ssl-certificate/select-certificate.png" alt-text="Screenshot that shows selecting certificate."::: ++ 1. After the self-hosted integration runtime node is registered: ++ > [!Note] + > The self-hosted integration runtime can change the remote access settings only when it has **single node**, which is by design. Otherwise, the radio button cannot be checked. + + :::image type="content" source="./media/tutorial-enable-remote-access-intranet-tls-ssl-certificate/enable-with-tls-ssl-certificate-advanced.png" alt-text="Screenshot that shows enabling with TLS/SSL certificate (Advanced)."::: ++ 1. Go to self-hosted **Integration Runtime Configuration Manager** -> **Settings** -> **Remote access from intranet**. Click **Change**. + 1. Choose **Enable with TLS/SSL certificate (Advanced)**. + 1. Click **Select**. In the pop-up window, choose the right certificate and select **OK**. ++ :::image type="content" source="./media/tutorial-enable-remote-access-intranet-tls-ssl-certificate/choose-tls-ssl-certificate.png" alt-text="Screenshot that shows choosing certificate."::: ++ 1. Verify the remote access settings in self-hosted **Integration Runtime Configuration Manager**. + + :::image type="content" source="./media/tutorial-enable-remote-access-intranet-tls-ssl-certificate/verify-remote-access-settings-1.png" alt-text="Screenshot that shows verifying the remote access settings in Self-hosted Integration Runtime Configuration Manager step 1."::: ++ :::image type="content" source="./media/tutorial-enable-remote-access-intranet-tls-ssl-certificate/verify-remote-access-settings-2.png" alt-text="Screenshot that shows verifying the remote access settings in Self-hosted Integration Runtime Configuration Manager step 2."::: ++5. Using a self-signed certificate if you donΓÇÖt have the publicly trusted certificate: + 1. Generate and export a self-signed certificate (this step can be skipped if you already have the certificate): + 1. Generate a self-signed certificate via PowerShell (with elevated privileges): + + ```Powershell + New-SelfSignedCertificate -DnsName contoso.com, node1.domain.contoso.com, node2.domain.contoso.com -Provider "Microsoft Enhanced RSA and AES Cryptographic Provider" -CertStoreLocation cert:\LocalMachine\My + ``` + 1. To export the generated certificate with a private key to a password protected PFX file, you will need its thumbprint. It can be copied from the results of `New-SelfSignedCertificate` command. For example, it is `CEB5B4372AA7BF877E56BCE27542F9F0A1AD197F`. + 1. Export the generated certificate with the private key via PowerShell (with elevated privileges): + + ```Powershell + $CertPassword = ConvertTo-SecureString -String ΓÇ£PasswordΓÇ¥ -Force ΓÇôAsPlainText + Export-PfxCertificate -Cert + cert:\LocalMachine\My\CEB5B4372AA7BF877E56BCE27542F9F0A1AD197F -FilePath C:\self-signedcertificate.pfx -Password $CertPassword + ``` + 1. You have exported the certificate with the private key to *C:\self-signedcertificate.pfx*. ++ 1. Install the certificate on all nodes to: **Local Machine** -> **Trusted Root Certification Authorities store**: + 1. Click on the certificate and install it. + 1. Select **Local Machine** and enter the password. + 1. Select **Place all certificates in the following store**. Click Browse. Select **Trusted Root Certification Authorities**. + 1. Select **Finish** to install the certificate. + + :::image type="content" source="./media/tutorial-enable-remote-access-intranet-tls-ssl-certificate/install-certificate-on-all-nodes.png" alt-text="Screenshot that shows install the certificate on all nodes."::: ++6. Troubleshooting + 1. Verify the certificate exists in the target store: + 1. Follow this procedure [How to: View certificates with the MMC snap-in - WCF](/dotnet/framework/wcf/feature-details/how-to-view-certificates-with-the-mmc-snap-in#view-certificates-in-the-mmc-snap-in) to view Certificates (Local Computer) in the MMC snap-in. + + :::image type="content" source="./media/tutorial-enable-remote-access-intranet-tls-ssl-certificate/view-certificates-mmc-snap-in.png" alt-text="Screenshot that shows viewing certificates in MMC snap in." lightbox="./media/tutorial-enable-remote-access-intranet-tls-ssl-certificate/view-certificates-mmc-snap-in-expanded.png"::: ++ 1. Confirm the certificate is installed in **Personal** and **Trusted Root Certification Authorities store** (If it is a self-signed certificate). ++ :::image type="content" source="./media/tutorial-enable-remote-access-intranet-tls-ssl-certificate/certificate-personal-trusted-root-certification-authorities.png" alt-text="Screenshot that shows the certificate installed in Personal and Trusted Root Certification Authorities store."::: ++ 1. Verify the certificate has a private key and isnΓÇÖt expired. + + :::image type="content" source="./media/tutorial-enable-remote-access-intranet-tls-ssl-certificate/verify-certificate.png" alt-text="Screenshot that shows verifying the certificate has a private key and isnΓÇÖt expired."::: ++ 1. Make sure the service account for the self-hosted integration runtime (default account is **NT SERVICE\DIAHostService**) has read permission to the private keys of certificate: + 1. Right click on the certificate -> **All Tasks** -> **Manage Private Keys**. + 1. If no, grant the permission, **Apply** and save. + + :::image type="content" source="./media/tutorial-enable-remote-access-intranet-tls-ssl-certificate/ensure-read-permission-to-certificate-private-keys.png" alt-text="Screenshot that shows the Service account for the self-hosted integration runtime has read permission to the private keys of certificate."::: + |
hdinsight | Hdinsight Release Notes Archive | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/hdinsight/hdinsight-release-notes-archive.md | description: Archived release notes for Azure HDInsight. Get development tips an Previously updated : 07/27/2021 Last updated : 12/27/2021 # Archived release notes Last updated 07/27/2021 Azure HDInsight is one of the most popular services among enterprise customers for open-source Apache Hadoop and Apache Spark analytics on Azure. -## Price Correction for HDInsight Dv2 Virtual Machines +## Release date: 07/27/2021 ++This release applies for both HDInsight 3.6 and HDInsight 4.0. HDInsight release is made available to all regions over several days. The release date here indicates the first region release date. If you don't see below changes, wait for the release being live in your region in several days. ++The OS versions for this release are: +- HDInsight 3.6: Ubuntu 16.04.7 LTS +- HDInsight 4.0: Ubuntu 18.04.5 LTS ++### New features +#### Azure HDInsight support for Restricted Public Connectivity is generally available on Oct 15 2021 +Azure HDInsight now supports restricted public connectivity in all regions. Below are some of the key highlights of this capability: ++- Ability to reverse resource provider to cluster communication such that it's outbound from the cluster to the resource provider +- Support for bringing your own Private Link enabled resources (e.g. storage, SQL, key vault) for HDinsight cluster to access the resources over private network only +- No public IP addresses are resource provisioned ++By using this new capability, you can also skip the inbound network security group (NSG) service tag rules for HDInsight management IPs. Learn more about [restricting public connectivity](./hdinsight-restrict-public-connectivity.md) ++#### Azure HDInsight support for Azure Private Link is generally available on Oct 15 2021 +You can now use private endpoints to connect to your HDInsight clusters over private link. Private link can be leveraged in cross VNET scenarios where VNET peering is not available or enabled. ++Azure Private Link enables you to access Azure PaaS Services (for example, Azure Storage and SQL Database) and Azure hosted customer-owned/partner services over a [private endpoint](../private-link/private-endpoint-overview.md) in your virtual network. ++Traffic between your virtual network and the service travels the Microsoft backbone network. Exposing your service to the public internet is no longer necessary. ++Let more at [enable private link](./hdinsight-private-link.md).  ++#### New Azure Monitor integration experience (Preview) +The new Azure monitor integration experience will be Preview in East US and West Europe with this release. Learn more details about the new Azure monitor experience [here](./log-analytics-migration.md#migrate-to-the-new-azure-monitor-integration). ++### Deprecation +#### Basic support for HDInsight 3.6 starting July 1, 2021 +Starting July 1, 2021, Microsoft offers [Basic support](hdinsight-component-versioning.md#support-options-for-hdinsight-versions) for certain HDInsight 3.6 cluster types. The Basic support plan will be available until 3 April 2022. You are automatically enrolled in Basic support starting July 1, 2021. No action is required by you to opt in. See [our documentation](hdinsight-36-component-versioning.md) for which cluster types are included under Basic support. ++We don't recommend building any new solutions on HDInsight 3.6, freeze changes on existing 3.6 environments. We recommend that you [migrate your clusters to HDInsight 4.0](hdinsight-version-release.md#how-to-upgrade-to-hdinsight-40). Learn more about [what's new in HDInsight 4.0](hdinsight-version-release.md#whats-new-in-hdinsight-40). ++### Behavior changes +#### HDInsight Interactive Query only supports schedule-based Autoscale +As customer scenarios grow more mature and diverse, we have identified some limitations with Interactive Query (LLAP) load-based Autoscale. These limitations are caused by the nature of LLAP query dynamics, future load prediction accuracy issues, and issues in the LLAP scheduler's task redistribution. Due to these limitations, users may see their queries run slower on LLAP clusters when Autoscale is enabled. The effect on performance can outweigh the cost benefits of Autoscale. ++Starting from July 2021, the Interactive Query workload in HDInsight only supports schedule-based Autoscale. You can no longer enable load-based autoscale on new Interactive Query clusters. Existing running clusters can continue to run with the known limitations described above. ++Microsoft recommends that you move to a schedule-based Autoscale for LLAP. You can analyze your cluster's current usage pattern through the Grafana Hive dashboard. For more information, see [Automatically scale Azure HDInsight clusters](hdinsight-autoscale-clusters.md). ++### Upcoming changes +The following changes will happen in upcoming releases. ++#### Built-in LLAP component in ESP Spark cluster will be removed +HDInsight 4.0 ESP Spark cluster has built-in LLAP components running on both head nodes. The LLAP components in ESP Spark cluster were originally added for HDInsight 3.6 ESP Spark, but has no real user case for HDInsight 4.0 ESP Spark. In the next release scheduled in Sep 2021, HDInsight will remove the built-in LLAP component from HDInsight 4.0 ESP Spark cluster. This change will help to offload head node workload and avoid confusion between ESP Spark and ESP Interactive Hive cluster type. ++### New region +- West US 3 +- Jio India West +- Australia Central ++### Component version change +The following component version has been changed with this release: +- ORC version from 1.5.1 to 1.5.9 ++You can find the current component versions for HDInsight 4.0 and HDInsight 3.6 in [this doc](./hdinsight-component-versioning.md). ++### Back ported JIRAs +Here are the back ported Apache JIRAs for this release: ++| Impacted Feature | Apache JIRA | +||--| +| Date / Timestamp | [HIVE-25104](https://issues.apache.org/jira/browse/HIVE-25104) | +| | [HIVE-24074](https://issues.apache.org/jira/browse/HIVE-24074) | +| | [HIVE-22840](https://issues.apache.org/jira/browse/HIVE-22840) | +| | [HIVE-22589](https://issues.apache.org/jira/browse/HIVE-22589) | +| | [HIVE-22405](https://issues.apache.org/jira/browse/HIVE-22405) | +| | [HIVE-21729](https://issues.apache.org/jira/browse/HIVE-21729) | +| | [HIVE-21291](https://issues.apache.org/jira/browse/HIVE-21291) | +| | [HIVE-21290](https://issues.apache.org/jira/browse/HIVE-21290) | +| UDF | [HIVE-25268](https://issues.apache.org/jira/browse/HIVE-25268) | +| | [HIVE-25093](https://issues.apache.org/jira/browse/HIVE-25093) | +| | [HIVE-22099](https://issues.apache.org/jira/browse/HIVE-22099) | +| | [HIVE-24113](https://issues.apache.org/jira/browse/HIVE-24113) | +| | [HIVE-22170](https://issues.apache.org/jira/browse/HIVE-22170) | +| | [HIVE-22331](https://issues.apache.org/jira/browse/HIVE-22331) | +| ORC | [HIVE-21991](https://issues.apache.org/jira/browse/HIVE-21991) | +| | [HIVE-21815](https://issues.apache.org/jira/browse/HIVE-21815) | +| | [HIVE-21862](https://issues.apache.org/jira/browse/HIVE-21862) | +| Table Schema | [HIVE-20437](https://issues.apache.org/jira/browse/HIVE-20437) | +| | [HIVE-22941](https://issues.apache.org/jira/browse/HIVE-22941) | +| | [HIVE-21784](https://issues.apache.org/jira/browse/HIVE-21784) | +| | [HIVE-21714](https://issues.apache.org/jira/browse/HIVE-21714) | +| | [HIVE-18702](https://issues.apache.org/jira/browse/HIVE-18702) | +| | [HIVE-21799](https://issues.apache.org/jira/browse/HIVE-21799) | +| | [HIVE-21296](https://issues.apache.org/jira/browse/HIVE-21296) | +| Workload Management | [HIVE-24201](https://issues.apache.org/jira/browse/HIVE-24201) | +| Compaction | [HIVE-24882](https://issues.apache.org/jira/browse/HIVE-24882) | +| | [HIVE-23058](https://issues.apache.org/jira/browse/HIVE-23058) | +| | [HIVE-23046](https://issues.apache.org/jira/browse/HIVE-23046) | +| Materialized view | [HIVE-22566](https://issues.apache.org/jira/browse/HIVE-22566) | ++### Price Correction for HDInsight Dv2 Virtual Machines A pricing error was corrected on April 25th, 2021, for the Dv2 VM series on HDInsight. The pricing error resulted in a reduced charge on some customer's bills prior to April 25th, and with the correction, prices now match what had been advertised on the HDInsight pricing page and the HDInsight pricing calculator. The pricing error impacted customers in the following regions who used Dv2 VMs: |
hdinsight | Hdinsight Release Notes | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/hdinsight/hdinsight-release-notes.md | description: Latest release notes for Azure HDInsight. Get development tips and Previously updated : 10/15/2021 Last updated : 12/27/2021 # Azure HDInsight release notes This article provides information about the **most recent** Azure HDInsight rele ## Summary Azure HDInsight is one of the most popular services among enterprise customers for open-source analytics on Azure.- If you would like to subscribe on release notes, watch releases on [this GitHub repository](https://github.com/hdinsight/release-notes/releases). -## Release date: 07/27/2021 +## Release date: 12/27/2021 -This release applies for both HDInsight 3.6 and HDInsight 4.0. HDInsight release is made available to all regions over several days. The release date here indicates the first region release date. If you don't see below changes, wait for the release being live in your region in several days. +This release applies for both HDInsight 4.0. HDInsight release is made available to all regions over several days. The release date here indicates the first region release date. If you don't see below changes, wait for the release being live in your region over several days. The OS versions for this release are:-- HDInsight 3.6: Ubuntu 16.04.7 LTS - HDInsight 4.0: Ubuntu 18.04.5 LTS -## New features -### Azure HDInsight support for Restricted Public Connectivity is generally available on Oct 15 2021 -Azure HDInsight now supports restricted public connectivity in all regions. Below are some of the key highlights of this capability: --- Ability to reverse resource provider to cluster communication such that it's outbound from the cluster to the resource provider -- Support for bringing your own Private Link enabled resources (e.g. storage, SQL, key vault) for HDinsight cluster to access the resources over private network only -- No public IP addresses are resource provisioned --By using this new capability, you can also skip the inbound network security group (NSG) service tag rules for HDInsight management IPs. Learn more about [restricting public connectivity](./hdinsight-restrict-public-connectivity.md) --### Azure HDInsight support for Azure Private Link is generally available on Oct 15 2021 -You can now use private endpoints to connect to your HDInsight clusters over private link. Private link can be leveraged in cross VNET scenarios where VNET peering is not available or enabled. --Azure Private Link enables you to access Azure PaaS Services (for example, Azure Storage and SQL Database) and Azure hosted customer-owned/partner services over a [private endpoint](../private-link/private-endpoint-overview.md) in your virtual network. --Traffic between your virtual network and the service travels the Microsoft backbone network. Exposing your service to the public internet is no longer necessary. --Let more at [enable private link](./hdinsight-private-link.md).  --### New Azure Monitor integration experience (Preview) -The new Azure monitor integration experience will be Preview in East US and West Europe with this release. Learn more details about the new Azure monitor experience [here](./log-analytics-migration.md#migrate-to-the-new-azure-monitor-integration). --## Deprecation -### Basic support for HDInsight 3.6 starting July 1, 2021 -Starting July 1, 2021, Microsoft offers [Basic support](hdinsight-component-versioning.md#support-options-for-hdinsight-versions) for certain HDInsight 3.6 cluster types. The Basic support plan will be available until 3 April 2022. You are automatically enrolled in Basic support starting July 1, 2021. No action is required by you to opt in. See [our documentation](hdinsight-36-component-versioning.md) for which cluster types are included under Basic support. --We don't recommend building any new solutions on HDInsight 3.6, freeze changes on existing 3.6 environments. We recommend that you [migrate your clusters to HDInsight 4.0](hdinsight-version-release.md#how-to-upgrade-to-hdinsight-40). Learn more about [what's new in HDInsight 4.0](hdinsight-version-release.md#whats-new-in-hdinsight-40). --## Behavior changes -### HDInsight Interactive Query only supports schedule-based Autoscale -As customer scenarios grow more mature and diverse, we have identified some limitations with Interactive Query (LLAP) load-based Autoscale. These limitations are caused by the nature of LLAP query dynamics, future load prediction accuracy issues, and issues in the LLAP scheduler's task redistribution. Due to these limitations, users may see their queries run slower on LLAP clusters when Autoscale is enabled. The effect on performance can outweigh the cost benefits of Autoscale. --Starting from July 2021, the Interactive Query workload in HDInsight only supports schedule-based Autoscale. You can no longer enable load-based autoscale on new Interactive Query clusters. Existing running clusters can continue to run with the known limitations described above. --Microsoft recommends that you move to a schedule-based Autoscale for LLAP. You can analyze your cluster's current usage pattern through the Grafana Hive dashboard. For more information, see [Automatically scale Azure HDInsight clusters](hdinsight-autoscale-clusters.md). --## Upcoming changes -The following changes will happen in upcoming releases. --### Built-in LLAP component in ESP Spark cluster will be removed -HDInsight 4.0 ESP Spark cluster has built-in LLAP components running on both head nodes. The LLAP components in ESP Spark cluster were originally added for HDInsight 3.6 ESP Spark, but has no real user case for HDInsight 4.0 ESP Spark. In the next release scheduled in Sep 2021, HDInsight will remove the built-in LLAP component from HDInsight 4.0 ESP Spark cluster. This change will help to offload head node workload and avoid confusion between ESP Spark and ESP Interactive Hive cluster type. --## New region -- West US 3-- Jio India West-- Australia Central--## Component version change -The following component version has been changed with this release: -- ORC version from 1.5.1 to 1.5.9--You can find the current component versions for HDInsight 4.0 and HDInsight 3.6 in [this doc](./hdinsight-component-versioning.md). --## Back ported JIRAs -Here are the back ported Apache JIRAs for this release: +HDInsight 4.0 image has been updated to mitigate Log4j vulnerability as described in [Microsoft’s Response to CVE-2021-44228 Apache Log4j 2.](https://msrc-blog.microsoft.com/2021/12/11/microsofts-response-to-cve-2021-44228-apache-log4j2/) -| Impacted Feature | Apache JIRA | -||--| -| Date / Timestamp | [HIVE-25104](https://issues.apache.org/jira/browse/HIVE-25104) | -| | [HIVE-24074](https://issues.apache.org/jira/browse/HIVE-24074) | -| | [HIVE-22840](https://issues.apache.org/jira/browse/HIVE-22840) | -| | [HIVE-22589](https://issues.apache.org/jira/browse/HIVE-22589) | -| | [HIVE-22405](https://issues.apache.org/jira/browse/HIVE-22405) | -| | [HIVE-21729](https://issues.apache.org/jira/browse/HIVE-21729) | -| | [HIVE-21291](https://issues.apache.org/jira/browse/HIVE-21291) | -| | [HIVE-21290](https://issues.apache.org/jira/browse/HIVE-21290) | -| UDF | [HIVE-25268](https://issues.apache.org/jira/browse/HIVE-25268) | -| | [HIVE-25093](https://issues.apache.org/jira/browse/HIVE-25093) | -| | [HIVE-22099](https://issues.apache.org/jira/browse/HIVE-22099) | -| | [HIVE-24113](https://issues.apache.org/jira/browse/HIVE-24113) | -| | [HIVE-22170](https://issues.apache.org/jira/browse/HIVE-22170) | -| | [HIVE-22331](https://issues.apache.org/jira/browse/HIVE-22331) | -| ORC | [HIVE-21991](https://issues.apache.org/jira/browse/HIVE-21991) | -| | [HIVE-21815](https://issues.apache.org/jira/browse/HIVE-21815) | -| | [HIVE-21862](https://issues.apache.org/jira/browse/HIVE-21862) | -| Table Schema | [HIVE-20437](https://issues.apache.org/jira/browse/HIVE-20437) | -| | [HIVE-22941](https://issues.apache.org/jira/browse/HIVE-22941) | -| | [HIVE-21784](https://issues.apache.org/jira/browse/HIVE-21784) | -| | [HIVE-21714](https://issues.apache.org/jira/browse/HIVE-21714) | -| | [HIVE-18702](https://issues.apache.org/jira/browse/HIVE-18702) | -| | [HIVE-21799](https://issues.apache.org/jira/browse/HIVE-21799) | -| | [HIVE-21296](https://issues.apache.org/jira/browse/HIVE-21296) | -| Workload Management | [HIVE-24201](https://issues.apache.org/jira/browse/HIVE-24201) | -| Compaction | [HIVE-24882](https://issues.apache.org/jira/browse/HIVE-24882) | -| | [HIVE-23058](https://issues.apache.org/jira/browse/HIVE-23058) | -| | [HIVE-23046](https://issues.apache.org/jira/browse/HIVE-23046) | -| Materialized view | [HIVE-22566](https://issues.apache.org/jira/browse/HIVE-22566) | +> [!Note] +> * Any new HDInsight 4.0 clusters created post 27 December 2021 00:00 UTC, need to be patched/rebooted. +> * For new HDInsight 4.0 clusters created between 16 Dec 2021 at 01:15 UTC and 27 Dec 2021 00:00 UTC, HDInsight 3.6 or in pinned subscriptions after 16 Dec 2021 the patch is auto applied within the hour in which the cluster is created, however customers must then reboot their nodes for the patching to complete (except for Kafka Management nodes, which are automatically rebooted). |
hdinsight | Migrate Versions | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/hdinsight/spark/migrate-versions.md | Last updated 05/20/2020 This document explains how to migrate Apache Spark workloads on Spark 2.1 and 2.2 to 2.3 or 2.4. -As discussed in the [Release Notes](../hdinsight-release-notes.md#upcoming-changes), starting July 1, 2020, the following cluster configurations will not be supported and customers will not be able to create new clusters with these configurations: +As discussed in the [Release Notes](../hdinsight-release-notes-archive.md), starting July 1, 2020, the following cluster configurations will not be supported and customers will not be able to create new clusters with these configurations: - Spark 2.1 and 2.2 in an HDInsight 3.6 Spark cluster - Spark 2.3 in an HDInsight 4.0 Spark cluster |
site-recovery | Hyper V Azure Support Matrix | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/site-recovery/hyper-v-azure-support-matrix.md | Guest VM network: Static IP (Windows) | Yes | Yes Guest VM network: Static IP (Linux) | No | No Guest VM network: Multi-NIC | Yes | Yes Https Proxy | No | No+Automatic Private IP Addressing (APIPA) | No | No Private link access to Site Recovery service | Yes. [Learn more](hybrid-how-to-enable-replication-private-endpoints.md). | Yes. [Learn more](hybrid-how-to-enable-replication-private-endpoints.md). |
static-web-apps | Configuration | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/static-web-apps/configuration.md | See the [example configuration](#example-configuration-file) file for details. ## Routes -Route rules allow you to define the pattern of URLs that allow access to your application to the web. Routes are defined as an array of routing rules. See the [example configuration file](#example-configuration-file) for usage examples. +You can define rules for one or more routes in your static web app. Route rules allow you to restrict access to users in specific roles or perform actions such as redirect or rewrite. Routes are defined as an array of routing rules. See the [example configuration file](#example-configuration-file) for usage examples. - Rules are defined in the `routes` array, even if you only have one route.-- Rules are executed in the order as they appear in the `routes` array.-- Rule evaluation stops at the first match - routing rules aren't chained together.-- You have full control over custom role names.- - There are a few built-in role names which include [`anonymous`](./authentication-authorization.md) and [`authenticated`](./authentication-authorization.md). +- Rules are evaluated in the order as they appear in the `routes` array. +- Rule evaluation stops at the first match. A match occurs when the `route` property and a value in the `methods` array (if specified) match the request. Each request can match at most one rule. The routing concerns significantly overlap with authentication (identifying the user) and authorization (assigning abilities to the user) concepts. Make sure to read the [authentication and authorization](authentication-authorization.md) guide along with this article. -The default file for static content is the _https://docsupdatetracker.net/index.html_ file. --## Defining routes +### Defining routes Each rule is composed of a route pattern, along with one or more of the optional rule properties. Route rules are defined in the `routes` array. See the [example configuration file](#example-configuration-file) for usage examples. +> [!IMPORTANT] +> Only the `route` and `methods` (if specified) properties are used to determine whether a rule matches a request. + | Rule property | Required | Default value | Comment | |--|--|--|--|-| `route` | Yes | n/a | The route pattern requested by the caller.<ul><li>[Wildcards](#wildcards) are supported at the end of route paths.<ul><li>For instance, the route _admin/\*_ matches any route under the _admin_ path.</ul></ul> | -| `rewrite` | No | n/a | Defines the file or path returned from the request.<ul><li>Is mutually exclusive to a `redirect` rule<li>Rewrite rules don't change the browser's location.<li>Values must be relative to the root of the app</ul> | +| `route` | Yes | n/a | The route pattern requested by the caller.<ul><li>[Wildcards](#wildcards) are supported at the end of route paths.<ul><li>For instance, the route _/admin\*_ matches any route beginning with _/admin_.</ul></ul> | +| `methods` | No | All methods | Defines an array of request methods which match a route. Available methods include: `GET`, `HEAD`, `POST`, `PUT`, `DELETE`, `CONNECT`, `OPTIONS`, `TRACE`, and `PATCH`. | +| `rewrite` | No | n/a | Defines the file or path returned from the request.<ul><li>Is mutually exclusive to a `redirect` rule.<li>Rewrite rules don't change the browser's location.<li>Values must be relative to the root of the app.</ul> | | `redirect` | No | n/a | Defines the file or path redirect destination for a request.<ul><li>Is mutually exclusive to a `rewrite` rule.<li>Redirect rules change the browser's location.<li>Default response code is a [`302`](https://developer.mozilla.org/docs/Web/HTTP/Status/302) (temporary redirect), but you can override with a [`301`](https://developer.mozilla.org/docs/Web/HTTP/Status/301) (permanent redirect).</ul> |-| `allowedRoles` | No | anonymous | Defines a list of role names required to access a route. <ul><li>Valid characters include `a-z`, `A-Z`, `0-9`, and `_`.<li>The built-in role, [`anonymous`](./authentication-authorization.md), applies to all unauthenticated users<li>The built-in role, [`authenticated`](./authentication-authorization.md), applies to any logged-in user.<li>Users must belong to at least one role.<li>Roles are matched on an _OR_ basis.<ul><li>If a user is in any of the listed roles, then access is granted.</ul><li>Individual users are associated to roles through [invitations](authentication-authorization.md).</ul> | +| `statusCode` | No | `301` or `302` for redirects | The [HTTP status code](https://developer.mozilla.org/docs/Web/HTTP/Status) of the response. | | `headers`<a id="route-headers"></a> | No | n/a | Set of [HTTP headers](https://developer.mozilla.org/docs/Web/HTTP/Headers) added to the response. <ul><li>Route-specific headers override [`globalHeaders`](#global-headers) when the route-specific header is the same as the global header is in the response.<li>To remove a header, set the value to an empty string.</ul> |-| `statusCode` | No | `200`, `301`, or `302` for redirects | The [HTTP status code](https://developer.mozilla.org/docs/Web/HTTP/Status) of the response. | -| `methods` | No | All methods | List of request methods which match a route. Available methods include: `GET`, `HEAD`, `POST`, `PUT`, `DELETE`, `CONNECT`, `OPTIONS`, `TRACE`, and `PATCH`. | +| `allowedRoles` | No | anonymous | Defines an array of role names required to access a route. <ul><li>Valid characters include `a-z`, `A-Z`, `0-9`, and `_`.<li>The built-in role, [`anonymous`](./authentication-authorization.md), applies to all users.<li>The built-in role, [`authenticated`](./authentication-authorization.md), applies to any logged-in user.<li>Users must belong to at least one role.<li>Roles are matched on an _OR_ basis.<ul><li>If a user is in any of the listed roles, then access is granted.</ul><li>Individual users are associated to roles through [invitations](authentication-authorization.md).</ul> | Each property has a specific purpose in the request/response pipeline. | Purpose | Properties | |--|--| | Match routes | `route`, `methods` |-| Authorize after a route is matched | `allowedRoles` | | Process after a rule is matched and authorized | `rewrite` (modifies request) <br><br>`redirect`, `headers`, `statusCode` (modifies response) |+| Authorize after a route is matched | `allowedRoles` | -## Securing routes with roles +### Specifying route patterns -Routes are secured by adding one or more role names into a rule's `allowedRoles` array. See the [example configuration file](#example-configuration-file) for usage examples. +The `route` property can be an exact route or a wildcard pattern. -By default, every user belongs to the built-in `anonymous` role, and all logged-in users are members of the `authenticated` role. Optionally, users are associated to custom roles via [invitations](./authentication-authorization.md). +#### Exact route -For instance, to restrict a route to only authenticated users, add the built-in `authenticated` role to the `allowedRoles` array. +To define an exact route, place the full path of the file in the `route` property. ```json {- "route": "/profile", + "route": "/profile/https://docsupdatetracker.net/index.html", "allowedRoles": ["authenticated"] } ``` -You can create new roles as needed in the `allowedRoles` array. To restrict a route to only administrators, you could define your own role named `administrator`, in the `allowedRoles` array. +This rule matches requests for the file _/profile/https://docsupdatetracker.net/index.html_. Because _https://docsupdatetracker.net/index.html_ is the default file, the rule also matches requests for the folder (_/profile_ or _/profile/_). -```json -{ - "route": "/admin", - "allowedRoles": ["administrator"] -} -``` --- You have full control over role names; there's no list to which your roles must adhere.-- Individual users are associated to roles through [invitations](authentication-authorization.md).+> [!IMPORTANT] +> If you use a folder path (`/profile` or `/profile/`) in the `route` property, it won't match requests for the file _/profile/https://docsupdatetracker.net/index.html_. When protecting a route that serves a file, always use the full path of the file such as `/profile/https://docsupdatetracker.net/index.html`. -## Wildcards +#### <a name="wildcards"></a>Wildcard pattern Wildcard rules match all requests in a route pattern, are only supported at the end of a path, and may be filtered by file extension. See the [example configuration file](#example-configuration-file) for usage examples. For instance, to implement routes for a calendar application, you can rewrite al ```json {- "route": "/calendar/*", + "route": "/calendar*", "rewrite": "/calendar.html" } ``` The _calendar.html_ file can then use client-side routing to serve a different view for URL variations like `/calendar/january/1`, `/calendar/2020`, and `/calendar/overview`. +> [!NOTE] +> A route pattern of `/calendar/*` matches all requests under the _/calendar/_ path. However, it will not match requests for the paths _/calendar_ or _/calendar.html_. Use `/calendar*` to match all requests that begin with _/calendar_. + You can filter wildcard matches by file extension. For instance, if you wanted to add a rule that only matches HTML files in a given path you could create the following rule: ```json To filter on multiple file extensions, you include the options in curly braces, Common uses cases for wildcard routes include: - Serving a specific file for an entire path pattern-- Mapping different HTTP methods to an entire path pattern - Enforcing authentication and authorization rules-- Implement specialized caching rules+- Implementing specialized caching rules ++### Securing routes with roles ++Routes are secured by adding one or more role names into a rule's `allowedRoles` array. See the [example configuration file](#example-configuration-file) for usage examples. ++By default, every user belongs to the built-in `anonymous` role, and all logged-in users are members of the `authenticated` role. Optionally, users are associated to custom roles via [invitations](./authentication-authorization.md). ++For instance, to restrict a route to only authenticated users, add the built-in `authenticated` role to the `allowedRoles` array. ++```json +{ + "route": "/profile*", + "allowedRoles": ["authenticated"] +} +``` ++You can create new roles as needed in the `allowedRoles` array. To restrict a route to only administrators, you could define your own role named `administrator`, in the `allowedRoles` array. ++```json +{ + "route": "/admin*", + "allowedRoles": ["administrator"] +} +``` ++- You have full control over role names; there's no list to which your roles must adhere. +- Individual users are associated to roles through [invitations](authentication-authorization.md). ++> [!IMPORTANT] +> When securing content, specify exact files when possible. If you have many files to secure, use wildcards after a shared prefix. For example: `/profile*` secures all possible routes that start with _/profile_, including _/profile_. ## Fallback routes Some common use cases for global headers include: - Encoding settings - Configuring cross-origin resource sharing ([CORS](https://developer.mozilla.org/docs/Web/HTTP/CORS)) -The following is an example of how to implement a custom CORS configuration. +The following example implements a custom CORS configuration. ```json { The following HTTP codes are available to override: |--|--|--| | [400](https://developer.mozilla.org/docs/Web/HTTP/Status/400) | Bad request | Invalid invitation link | | [401](https://developer.mozilla.org/docs/Web/HTTP/Status/401) | Unauthorized | Request to restricted pages while unauthenticated |-| [403](https://developer.mozilla.org/docs/Web/HTTP/Status/403) | Forbidden | <ul><li>User is logged in but doesn't have the roles required to view the page.<li>User is logged in but the runtime cannot get the user details from their identity claims.<li>There are too many users logged in to the site with custom roles, therefore the runtime can't login the user.</ul> | +| [403](https://developer.mozilla.org/docs/Web/HTTP/Status/403) | Forbidden | <ul><li>User is logged in but doesn't have the roles required to view the page.<li>User is logged in but the runtime cannot get the user details from their identity claims.<li>There are too many users logged in to the site with custom roles, therefore the runtime can't log in the user.</ul> | | [404](https://developer.mozilla.org/docs/Web/HTTP/Status/404) | Not found | File not found | The following example configuration demonstrates how to override an error code. The `networking` section controls the network configuration of your static web a > [!NOTE] > Networking configuration is only available in the Azure Static Web Apps Standard plan. -Define each IPv4 address block in Classless Inter-Domain Routing (CIDR) notation. To learn more about CIDR notation, see [Classless Inter-Domain Routing](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing). Each IPv4 address block can denote either a public or private address space. If you only want to allow access from a single IP Address you can use the `/32` CIDR block. +Define each IPv4 address block in Classless Inter-Domain Routing (CIDR) notation. To learn more about CIDR notation, see [Classless Inter-Domain Routing](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing). Each IPv4 address block can denote either a public or private address space. If you only want to allow access from a single IP Address, you can use the `/32` CIDR block. ```json { For example, the following configuration shows how you can add a unique identifi { "routes": [ {- "route": "/profile", + "route": "/profile*", "allowedRoles": ["authenticated"] }, {- "route": "/admin/*", + "route": "/admin/https://docsupdatetracker.net/index.html", "allowedRoles": ["administrator"] }, { For example, the following configuration shows how you can add a unique identifi "allowedRoles": ["authenticated"] }, {- "route": "/customers/contoso", + "route": "/customers/contoso*", "allowedRoles": ["administrator", "customers_contoso"] }, { For example, the following configuration shows how you can add a unique identifi "redirect": "/.auth/logout" }, {- "route": "/calendar/*", + "route": "/calendar*", "rewrite": "/calendar.html" }, { Based on the above configuration, review the following scenarios. | Requests to... | results in... | |--|--|-| _/profile_ | Authenticated users are served the _/profile/https://docsupdatetracker.net/index.html_ file. Unauthenticated users are redirected to _/login_. | -| _/admin/_ | Authenticated users in the _administrator_ role are served the _/admin/https://docsupdatetracker.net/index.html_ file. Authenticated users not in the _administrator_ role are served a `403` error<sup>1</sup>. Unauthenticated users are redirected to _/login_. | -| _/logo.png_ | Serves the image with a custom cache rule where the max age is a little over 182 days (15,770,000 seconds). | +| _/profile_ | Authenticated users are served the _/profile/https://docsupdatetracker.net/index.html_ file. Unauthenticated users are redirected to _/login_ by the `401` response override rule. | +| _/admin_, _/admin/_, or _/admin/https://docsupdatetracker.net/index.html_ | Authenticated users in the _administrator_ role are served the _/admin/https://docsupdatetracker.net/index.html_ file. Authenticated users not in the _administrator_ role are served a `403` error<sup>1</sup>. Unauthenticated users are redirected to _/login_ | +| _/images/logo.png_ | Serves the image with a custom cache rule where the max age is a little over 182 days (15,770,000 seconds). | | _/api/admin_ | `GET` requests from authenticated users in the _registeredusers_ role are sent to the API. Authenticated users not in the _registeredusers_ role and unauthenticated users are served a `401` error.<br/><br/>`POST`, `PUT`, `PATCH`, and `DELETE` requests from authenticated users in the _administrator_ role are sent to the API. Authenticated users not in the _administrator_ role and unauthenticated users are served a `401` error. | | _/customers/contoso_ | Authenticated users who belong to either the _administrator_ or _customers_contoso_ roles are served the _/customers/contoso/https://docsupdatetracker.net/index.html_ file. Authenticated users not in the _administrator_ or _customers_contoso_ roles are served a `403` error<sup>1</sup>. Unauthenticated users are redirected to _/login_. | | _/login_ | Unauthenticated users are challenged to authenticate with GitHub. | |
storage | Storage Redundancy | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/storage/common/storage-redundancy.md | The following table shows which redundancy options are supported by each type of | LRS | ZRS | GRS/RA-GRS | GZRS/RA-GZRS | |:-|:-|:-|:-|-| General-purpose v2<br /> General-purpose v1<br /> Premium block blob<br /> Legacy blob<br /> Premium file shares | General-purpose v2<br /> Premium block blobs<br /> Premium file shares | General-purpose v2<br /> General-purpose v1<br /> Legacy blob | General-purpose v2 | +| General-purpose v2<sup>1</sup><br /> General-purpose v1<br /> Premium block blob<sup>1</sup><br /> Legacy blob<br /> Premium file shares | General-purpose v2<sup>1</sup><br /> Premium block blobs<sup>1</sup><br /> Premium file shares | General-purpose v2<sup>1</sup><br /> General-purpose v1<br /> Legacy blob | General-purpose v2<sup>1</sup> | ++<sup>1</sup> Accounts of this type with a hierarchical namespace enabled also support the specified redundancy option. All data for all storage accounts is copied according to the redundancy option for the storage account. Objects including block blobs, append blobs, page blobs, queues, tables, and files are copied. Data in all tiers, including the archive tier, is copied. For more information about blob tiers, see [Hot, Cool, and Archive access tiers for blob data](../blobs/access-tiers-overview.md). For pricing information for each redundancy option, see [Azure Storage pricing]( > [!NOTE] > Azure Premium Disk Storage currently supports only locally redundant storage (LRS). Block blob storage accounts support locally redundant storage (LRS) and zone redundant storage (ZRS) in certain regions. +### Support for customer-managed account failover ++All geo-redundant offerings support Microsoft-managed failover in the event of a disaster in the primary region. In addition, some account types support customer-managed account failover, as shown in the following table. Supported account types must use Azure Resource Manager deployments. For more information about disaster recovery and customer-managed failover, see [Disaster recovery and storage account failover](storage-disaster-recovery-guidance.md). ++| Type of failover | GRS/RA-GRS | GZRS/RA-GZRS | +|||| +| **Customer-managed failover** | General-purpose v2 accounts</br> General-purpose v1 accounts</br> Legacy Blob Storage accounts | General-purpose v2 accounts | +| **Microsoft-managed failover** | All account types | General-purpose v2 accounts | ++> [!NOTE] +> Customer-managed account failover is not yet supported in accounts that have a hierarchical namespace (Azure Data Lake Storage Gen2). To learn more, see [Blob storage features available in Azure Data Lake Storage Gen2](../blobs/storage-feature-support-in-storage-accounts.md). +> +> In the event of a disaster that affects the primary region, Microsoft will manage the failover for accounts with a hierarchical namespace. For more information, see [Microsoft-managed failover](storage-disaster-recovery-guidance.md#microsoft-managed-failover). + ## Data integrity Azure Storage regularly verifies the integrity of data stored using cyclic redundancy checks (CRCs). If data corruption is detected, it is repaired using redundant data. Azure Storage also calculates checksums on all network traffic to detect corruption of data packets when storing or retrieving data. |
synapse-analytics | Overview Features | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/synapse-analytics/sql/overview-features.md | Consumption models in Synapse SQL enables you to use different database objects. | | Dedicated | Serverless | | | | |-| **Tables** | [Yes](/sql/t-sql/statements/create-table-azure-sql-data-warehouse?view=azure-sqldw-latest&preserve-view=true) | No, serverless model can query only external data placed on [Azure Storage](#storage-options) | -| **Views** | [Yes](/sql/t-sql/statements/create-view-transact-sql?view=azure-sqldw-latest&preserve-view=true). Views can use [query language elements](#query-language) that are available in dedicated model. | [Yes](/sql/t-sql/statements/create-view-transact-sql?view=azure-sqldw-latest&preserve-view=true). Views can use [query language elements](#query-language) that are available in serverless model. | -| **Schemas** | [Yes](/sql/t-sql/statements/create-schema-transact-sql?view=azure-sqldw-latest&preserve-view=true) | [Yes](/sql/t-sql/statements/create-schema-transact-sql?view=azure-sqldw-latest&preserve-view=true) | -| **Temporary tables** | [Yes](../sql-data-warehouse/sql-data-warehouse-tables-temporary.md?context=/azure/synapse-analytics/context/context) | No | -| **User defined procedures** | [Yes](/sql/t-sql/statements/create-procedure-transact-sql?view=azure-sqldw-latest&preserve-view=true) | Yes | -| **User defined functions** | [Yes](/sql/t-sql/statements/create-function-sql-data-warehouse?view=azure-sqldw-latest&preserve-view=true) | Yes, only inline table-valued functions. | -| **Triggers** | No | No | -| **External tables** | [Yes](/sql/t-sql/statements/create-external-table-transact-sql?view=azure-sqldw-latest&preserve-view=true). See supported [data formats](#data-formats). | [Yes](/sql/t-sql/statements/create-external-table-transact-sql?view=azure-sqldw-latest&preserve-view=true). See supported [data formats](#data-formats). | +| **Tables** | [Yes](/sql/t-sql/statements/create-table-azure-sql-data-warehouse?view=azure-sqldw-latest&preserve-view=true) | No, the in-database tables are not supported. Serverless SQL pool can query only [external tables](develop-tables-external-tables.md?tabs=native) that reference data placed on [Azure Storage](#storage-options) | +| **Views** | [Yes](/sql/t-sql/statements/create-view-transact-sql?view=azure-sqldw-latest&preserve-view=true). Views can use [query language elements](#query-language) that are available in dedicated model. | [Yes](/sql/t-sql/statements/create-view-transact-sql?view=azure-sqldw-latest&preserve-view=true), you can create views over [external tables](develop-tables-external-tables.md?tabs=native) and other views. Views can use [query language elements](#query-language) that are available in serverless model. | +| **Schemas** | [Yes](/sql/t-sql/statements/create-schema-transact-sql?view=azure-sqldw-latest&preserve-view=true) | [Yes](/sql/t-sql/statements/create-schema-transact-sql?view=azure-sqldw-latest&preserve-view=true), schemas are supported. | +| **Temporary tables** | [Yes](../sql-data-warehouse/sql-data-warehouse-tables-temporary.md?context=/azure/synapse-analytics/context/context) | No, temporary tables might be used just to store some information from system views. | +| **User defined procedures** | [Yes](/sql/t-sql/statements/create-procedure-transact-sql?view=azure-sqldw-latest&preserve-view=true) | Yes, stored procedures can be placed in any user databases (not `master` database). | +| **User defined functions** | [Yes](/sql/t-sql/statements/create-function-sql-data-warehouse?view=azure-sqldw-latest&preserve-view=true) | Yes, only inline table-valued functions. Scalar user defined functions are not supported. | +| **Triggers** | No | No, serverless SQL pools do not allow changing data, so the triggers cannot react on data changes. | +| **External tables** | [Yes](/sql/t-sql/statements/create-external-table-transact-sql?view=azure-sqldw-latest&preserve-view=true). See supported [data formats](#data-formats). | [Yes](/sql/t-sql/statements/create-external-table-transact-sql?view=azure-sqldw-latest&preserve-view=true). See the supported [data formats](#data-formats). | | **Caching queries** | Yes, multiple forms (SSD-based caching, in-memory, resultset caching). In addition, Materialized View are supported | No. Only file statistics are cached. | | **Table variables** | [No](/sql/t-sql/data-types/table-transact-sql?view=azure-sqldw-latest&preserve-view=true), use temporary tables | No, table variables are not supported. | | **[Table distribution](../sql-data-warehouse/sql-data-warehouse-tables-distribute.md?context=/azure/synapse-analytics/context/context)** | Yes | No, table distributions are not supported. | | **[Table indexes](../sql-data-warehouse/sql-data-warehouse-tables-index.md?context=/azure/synapse-analytics/context/context)** | Yes | No, indexes are not supported. |-| **[Table partitions](../sql-data-warehouse/sql-data-warehouse-tables-partition.md?context=/azure/synapse-analytics/context/context)** | Yes | No, only external tables that are synchronized form Apache Spark pools can be partitioned per folders. | +| **[Table partitions](../sql-data-warehouse/sql-data-warehouse-tables-partition.md?context=/azure/synapse-analytics/context/context)** | Yes | No, only external tables that are synchronized from the Apache Spark pools can be partitioned per folders. | | **[Statistics](develop-tables-statistics.md)** | Yes | Yes |-| **[Workload management, resource classes, and concurrency control](../sql-data-warehouse/resource-classes-for-workload-management.md?context=/azure/synapse-analytics/context/context)** | Yes | No | +| **Workload management, resource classes, and concurrency control** | Yes, see [workload management, resource classes, and concurrency control](../sql-data-warehouse/resource-classes-for-workload-management.md?context=/azure/synapse-analytics/context/context). | No, serverless SQL pool automatically manages the resources. | | **Cost control** | Yes, using scale-up and scale-down actions. | Yes, using [the Azure portal or T-SQL procedure](./data-processed.md#cost-control). | ## Query language |
synapse-analytics | Resources Self Help Sql On Demand | https://github.com/MicrosoftDocs/azure-docs/commits/master/articles/synapse-analytics/sql/resources-self-help-sql-on-demand.md | If the issue still continues, create a [support ticket](../../azure-portal/suppo If you do not see the databases that are created in serverless SQL pool, check is your serverless SQL pool started. If the serverless SQL pool is deactivated, the databases will not be shown. Execute any query (for example `SELECT 1`) on the serverless pool to activate it, and the databases will be shown. +### Synapse Serverless SQL pool is showing as unavailable +Wrong network configuration is often the cause for this behaviour. Make sure the ports are appropriatelly configured. In case you use firewall or Private Endpoint check their settings as well. Finally, make sure the appropriate roles are granted. + ## Storage access If you are getting the errors while trying to access the files on storage, make sure that you have permissions to access data. You should be able to access publicly available files. If you are accessing data without credentials, make sure that your Azure AD identity can directly access the files. |