diff --git a/.gitignore b/.gitignore deleted file mode 100644 index 2f381d857..000000000 --- a/.gitignore +++ /dev/null @@ -1,13 +0,0 @@ -log/ -obj/ -_site/ -.optemp/ -_themes*/ -_repo.*/ - -.openpublishing.buildcore.ps1 -/.vs -power-virtual-agents/.vscode/* -.vscode/* -.DS_Store -/power-virtual-agents/.vs diff --git a/.openpublishing.redirection.json b/.openpublishing.redirection.json index 82ffd7ca5..2ac0854c9 100644 --- a/.openpublishing.redirection.json +++ b/.openpublishing.redirection.json @@ -975,6 +975,11 @@ "source_path": "power-platform/admin/storage-sas-token.md", "redirect_url": "/power-platform/admin/access-storage", "redirect_document_id": false + }, + { + "source_path": "power-platform/admin/onpremises-data-gateway-source-management.md", + "redirect_url": "/power-platform/admin/wp-onpremises-gateway", + "redirect_document_id": false } ] } diff --git a/power-platform/admin/TOC.yml b/power-platform/admin/TOC.yml index baea8e06a..b74e01a45 100644 --- a/power-platform/admin/TOC.yml +++ b/power-platform/admin/TOC.yml @@ -814,7 +814,7 @@ href: create-dataverseapplicationuser.md - name: Tenant Settings items: - - name: "List tenant settings" + - name: List tenant settings (preview) href: list-tenantsettings.md - name: Data integration items: @@ -852,6 +852,8 @@ href: run-bulk-system-jobs-detect-duplicate-records.md - name: Bulk deletion href: delete-bulk-records.md + - name: Set address record settings + href: disable-delete-address-records.md - name: View and take action on bulk deletion jobs href: view-take-action-bulk-deletion-jobs.md - name: Restore deleted table records (preview) diff --git a/power-platform/admin/configure-relevance-search-organization.md b/power-platform/admin/configure-relevance-search-organization.md index 9ace7d3ab..93934efef 100644 --- a/power-platform/admin/configure-relevance-search-organization.md +++ b/power-platform/admin/configure-relevance-search-organization.md @@ -4,7 +4,7 @@ description: Configure Dataverse search to improve search results and performanc author: sericks007 ms.component: pa-admin ms.topic: conceptual -ms.date: 05/16/2024 +ms.date: 05/17/2024 ms.subservice: admin ms.author: sericks search.audienceType: @@ -14,7 +14,7 @@ contributors: --- # Configure Dataverse search for your environment -Dataverse search delivers fast and comprehensive search results in a single list, sorted by relevance. As an administrator or customizer, you can enable and configure Dataverse search as described in this article. Quick Find views are used for configuring Dataverse search, so you can manage global search, quick find, and lookup search behavior in one single place. +Dataverse search delivers fast and comprehensive search results in a single list, sorted by [relevance](/azure/search/index-similarity-and-scoring). As an administrator or customizer, you can turn on and configure Dataverse search as described in this article. Quick Find views are used for configuring Dataverse search, so you can manage global search, quick find, and lookup search behavior in one single place. With Dataverse search enabled, a search box is always available at the top of every page in all the model-driven apps in the **environment**. Once Dataverse search is enabled, it applies to all apps and can't be disabled per app. Users can start a new search and quickly find the information they're looking for, from the searchable tables included in the app. Dataverse search also becomes the default and only global search experience in all model-driven apps in the environment. Users won't be able to switch to [quick find search](/powerapps/user/quick-find) formerly known as categorized search. @@ -119,6 +119,8 @@ Setting up Dataverse search after enabling it in the **Power Platform admin cent 3. Ensure the tables enabled for Dataverse search are included in the model-driven app. Use the app designer to verify that the table is included in an app's components. For more information, see [Add or edit model-driven app components](/powerapps/maker/model-driven-apps/add-edit-app-components#add-a-component). +4. Make sure your table is customizable and that the settings to **Track changes** and **Appear in search results** in the **Advanced options** are both set to **On**. For more information, see [Create and edit tables using Power Apps](/power-apps/maker/data-platform/create-edit-entities-portal?tabs=excel). + ### Select tables for Dataverse search Setting up search starts with reviewing the tables that are enabled for Dataverse search, in context of a solution. Using the new solution explorer, you can see a snapshot of the Dataverse search index on the **Overview** page. diff --git a/power-platform/admin/create-users.md b/power-platform/admin/create-users.md index 9c39729cd..9a3bb0843 100644 --- a/power-platform/admin/create-users.md +++ b/power-platform/admin/create-users.md @@ -82,29 +82,29 @@ The following table shows the fields that are managed in the **Users** section o - + - - - - - - - - - - - - - - - + + + + + + + + + + + + + + +

Customer engagement apps user form

Microsoft 365/Microsoft Entra user

Customer engagement apps user form

Dataverse SystemUser objectMicrosoft 365/Microsoft Entra user
User NameUsername
Full Name* Display Name
Title Job title
First Name First Name
Last Name Last Name
Primary Email** Email
InternalEmailAddress*** Mail
Main Phone Office phone
Mobile Phone Mobile phone
Address Street address
Address City
Address State or province
Address Country or region
AzureActiveDirectoryObjectId**** ObjectId
* Full Name isn't automatically updated and synchronized with customer engagement apps.
** To prevent data loss, the Primary Email field isn't automatically updated and synchronized with customer engagement apps.
***InternalEmailAddress can be updated by customers; after which, sync will no longer update this field.
**** ObjectID of a user or a service principal in Microsoft Entra ID.
User NameDomainNameUsername
Full Name* Full Name Full Name
Title JobTitle Job title
First Name FirstName First Name
Last Name LastName Last Name
Primary Email**InternalEmailAddress***Mail
Main Phone Address1_Telephone1 Office phone
Mobile Phone MobilePhone Mobile phone
Street Address1_Line1 Street address
City Address1_City City
State/Province Address1_StateOrProvince State or province
Postal Code Address1_PostalCode Postal Code
Country Address1_Country Country or region
AzureActiveDirectoryObjectId**** AzureActiveDirectoryObjectId ObjectId
* Full Name isn't automatically updated and synchronized with customer engagement apps.
** To prevent data loss, the PrimaryEmail field isn't automatically updated and synchronized with customer engagement apps.
***InternalEmailAddress can be updated by customers; after which, sync will no longer update this field.
**** ObjectID of a user or a service principal in Microsoft Entra ID.
> [!NOTE] -> Custom fields are **never** synchronized between Microsoft 365, Microsoft Entra ID, and Power Platform. +> Custom fields are **never** synchronized between Microsoft 365, Microsoft Entra, and Power Platform. > > All the fields are **always** synchronized, except fields explicitly mentioned as not automatically updated (custom fields, Full Name, Primary Email, and Internal Email Address after a customer update). > diff --git a/power-platform/admin/disable-delete-address-records.md b/power-platform/admin/disable-delete-address-records.md new file mode 100644 index 000000000..775387e79 --- /dev/null +++ b/power-platform/admin/disable-delete-address-records.md @@ -0,0 +1,53 @@ +--- +title: Set address record settings +description: Learn how to prevent empty address records from being created and how to allow users to delete address data. +author: mkannapiran +ms.component: pa-admin +ms.topic: conceptual +ms.date: 05/17/2024 +ms.subservice: admin +ms.author: kamanick +ms.reviewer: sericks +search.audienceType: + - admin +--- + +# Set address record settings + +This article explains how to prevent empty address records from being created and how to allow users to delete address data. + +## Prevent empty address records from being created + +The **Disable empty address record creation** setting helps you prevent address record creation in Dataverse when there's no data in the address segment of a payload. This feature only supports **Account** and **Contact** tables in Dataverse. Any other table that is associated with an address isn't impacted by this setting. + +For example, suppose there's an incoming payload for the **Account** table and the address data is empty. If the **Disable empty address record creation** setting is set to **On**, it prevents an empty record from being created in Dataverse. However, if the same payload contains address data, then an address record is created in Dataverse. + +> [!Note] +> Turning on the **Disable empty address record creation** setting doesn't remove existing empty address records. + +Complete the following steps to prevent empty address records from being created. + +1. Sign in to the [Power Platform admin center](https://admin.powerplatform.microsoft.com). +1. Select **Environments** in the navigation pane. +1. Select the checkmark next to an environment, and then select **Settings** in the command bar. +1. Select **Product** > **Features**. +1. Find the **Disable Empty Address Record Creation** setting and turn it **On**. +1. Select **Save** on the bottom of the page to save the changes. + +## Allow users to delete address data + +The **Enable deletion of address records** setting allows a user to delete address data in Dataverse. The default setting for this setting is **Off**, which means that users can't delete address records in Dataverse. The address record deletion capability is applicable only for **Account** and **Contact** tables in Dataverse. + +Turning on the **Enable deletion of address records** setting allows address records to be deleted in the following ways: +- Through the user experience in Power Platform. +- Through bulk delete operations +- Through SDK. + +Complete the following steps to allow users to delete address data. + +1. Sign in to the [Power Platform admin center](https://admin.powerplatform.microsoft.com). +1. Select **Environments** in the navigation pane. +1. Select the checkmark next to an environment, and then select **Settings** in the command bar. +1. Select **Product** > **Features**. +1. Find the **Enable deletion of address records** setting and turn it **On**. +1. Select **Save** on the bottom of the page to save the changes. diff --git a/power-platform/admin/list-tenantsettings.md b/power-platform/admin/list-tenantsettings.md index 51bd4d4a3..6feccea17 100644 --- a/power-platform/admin/list-tenantsettings.md +++ b/power-platform/admin/list-tenantsettings.md @@ -5,12 +5,13 @@ author: laneswenka ms.reviewer: sericks ms.component: pa-admin ms.topic: reference -ms.date: 04/23/2024 +ms.date: 05/17/2024 ms.subservice: admin ms.author: laswenka search.audienceType: - admin contributors: +- arjunmayur - bibekTimalsina948 - dannylevymsft ms.collection: bap-ai-copilot @@ -77,7 +78,7 @@ The response is always a **200 OK** response, unless you aren't correctly authen "shareWithColleaguesUserLimit": 10000 }, "powerApps": { - "disableShareWithEveryone": false, + "disableShareWithEveryone": true, "enableGuestsToMake": false }, "modelExperimentation": { @@ -106,9 +107,8 @@ The response is always a **200 OK** response, unless you aren't correctly authen |powerPlatform.search.disableDocsSearch | Boolean | When this setting is true, users in the environment can see a message that indicates Microsoft Learn and documentation search categories have been turned off by the administrator. Default value is false.| |powerPlatform.search.disableCommunitySearch | Boolean | When this setting is true, users in the environment can see a message that indicates community and blog search categories have been turned off by the administrator. Default value is false.| |powerPlatform.search.disableBingVideoSearch | Boolean | When this setting is true, users in the environment can see a message that indicates video search categories have been turned off by the administrator. Default value is false.| -|powerPlatform.powerApps.disableShareWithEveryone | Boolean | Ability to disable the **Share with Everyone** capability for nonadmin users in all Power Apps. Default value is false.| +|powerPlatform.powerApps.disableShareWithEveryone | Boolean | Ability to turn off the **Share with Everyone** capability for nonadmin users in all Power Apps. Default value is true.| |powerPlatform.teamsIntegration.shareWithColleaguesUserLimit | Integer | Maximum value setting for the number of users in a security group used to share an app built using Power Apps on Microsoft Teams. Default value is 10000 but can be increased or decreased, as required.| -|powerPlatform.powerApps.disableShareWithEveryone | Boolean | Ability to disable the **Share with Everyone** capability in all Power Apps. Default value is false.| |powerPlatform.powerApps.DisableConnectionSharingWithEveryone | Boolean | Gets or sets a value indicating whether non-admin users in the tenant can share connections with everyone. Default value is false. | |powerPlatform.powerApps.enableGuestsToMake | Boolean | Ability to allow guest users in your tenant to create Power Apps. Default value is false.| |powerPlatform.powerApps.disableMembersIndicator | Boolean | This setting isn't currently used by the platform but might be used in the future.| diff --git a/power-platform/admin/media/get-new-features-early.png b/power-platform/admin/media/get-new-features-early.png index 2a0f52daa..96c204300 100644 Binary files a/power-platform/admin/media/get-new-features-early.png and b/power-platform/admin/media/get-new-features-early.png differ diff --git a/power-platform/admin/onpremises-data-gateway-source-management.md b/power-platform/admin/onpremises-data-gateway-source-management.md deleted file mode 100644 index f9b38f24a..000000000 --- a/power-platform/admin/onpremises-data-gateway-source-management.md +++ /dev/null @@ -1,97 +0,0 @@ ---- -title: "Manage data sources (preview) | MicrosoftDocs" -description: View and manage on-premises data sources. -ms.component: pa-admin -ms.topic: conceptual -ms.date: 05/11/2021 -author: arthiriyer -ms.subservice: admin -ms.author: arthii -ms.reviewer: sericks -search.audienceType: - - admin ---- -# Data source management (preview) - -[!INCLUDE [cc-beta-prerelease-disclaimer](../includes/cc-beta-prerelease-disclaimer.md)] - -On the **Data** page of the Power Platform admin center (https://admin.powerplatform.microsoft.com), you can view and manage Power BI cloud and on-premises data sources and gateway clusters. The on-premises data sources on this page include all on-premises data source definitions for gateways you administer. The cloud data sources on this page are cloud connections in your published Power BI reports. - -> [!IMPORTANT] -> - This is a preview feature. -> - Preview features aren’t meant for production use and may have restricted functionality. These features are available before an official release so that customers can get early access and provide feedback. -> - This feature is being gradually rolled out across regions and might not be available yet in your region. - -This article describes managing data sources. For information on managing gateway clusters, see [Preview: On-premises data gateway management](onpremises-data-gateway-management.md). - -> [!NOTE] -> The data sources tab will not be available for tenant or service administrators when **Tenant administration** is turned on. - -> [!div class="mx-imgBorder"] -> ![Data sources tab.](media/data-gateways-tenant-admin-off-data-sources.png "Data sources tab") - -- **Data Source Name**: The name of the data source. -- **Data source type**: The type of the data source. For supported data sources, see [Power BI data sources](/power-bi/connect-data/power-bi-data-sources). -- **Users**: Users who can use this data source in data sets and data flows. -- **Status**: Select (![Check status.](media/gateway-status.png "Check status")) to check the status of a gateway member. -- **Gateway cluster name**: The gateway cluster on which this data source was created. If it is a cloud data source, this value will be “Cloud”. - -## Data source settings - -Select a data source and then select **Settings** from the top menu bar to see the data source properties. You can view and update applicable data source properties.   - -> [!div class="mx-imgBorder"] -> ![Data source settings.](media/data-gateways-data-source-settings.png "Data source settings") - -## Add new data source - -Select **+New** from the top menu bar to create a new gateway data source. This can either be an on-premises or a VNet data source. - -Select a gateway cluster, data source name, a data source type, and other data source properties to create the data source. For more information on data source properties, see [Add or remove a gateway data source](/power-bi/connect-data/service-gateway-data-sources). - -:::image type="content" source="media/data-gateways-new-data-source.png" alt-text="New data source."::: - -## Remove a data source - -Select a data source and then select **Remove** to remove the data source. - -> [!div class="mx-imgBorder"] -> ![Remove a data source.](media/data-gateways-remove-data-source.png "Remove a data source") - -## Manage users - -Select a data source and then select **Manage users** to see the list of current data source users. These users can use this data source in published reports and data flows. - -> [!div class="mx-imgBorder"] -> ![Manage users for data source.](media/data-gateways-source-manage-users.png "Manage users for data source") - -## Get help -For faster troubleshooting and assistance, select **Get help** to open a Get help panel. Include the session ID in a customer support ticket for any issues on the Data Gateways feature in the Power Platform admin center. - -> [!div class="mx-imgBorder"] -> ![Get help.](media/get-help.png "Get help") - -## Region - -> [!div class="mx-imgBorder"] -> ![Data source regions.](media/data-gateways-data-source-region.png "Data source regions") - -Currently, data sources are available only for the default Power BI region. For other regions, you won't see any data sources. - -## Search - -Select **Search** to find data sources and see their details. You currently can search on data source names, data source types, and gateway cluster names, but not users and status. - -> [!div class="mx-imgBorder"] -> ![Search data sources.](media/data-gateways-data-source-search.png "Search data sources") - -## Data source status - -Select a data source, and then select **Check status** (![Data source status.](media/gateway-status.png "Data source status")) to see the status of a data source. - -### See also - [On-premises data gateway](/data-integration/gateway/service-gateway-onprem)
- [Connecting to on-premises data sources with On-premises Data Gateway](/azure/analysis-services/analysis-services-gateway)
- - -[!INCLUDE[footer-include](../includes/footer-banner.md)] diff --git a/power-platform/admin/settings-features.md b/power-platform/admin/settings-features.md index 9753d7ff4..107137d03 100644 --- a/power-platform/admin/settings-features.md +++ b/power-platform/admin/settings-features.md @@ -4,7 +4,7 @@ description: Manage feature settings to adjust how features appear and function author: sericks007 ms.component: pa-admin ms.topic: conceptual -ms.date: 05/15/2024 +ms.date: 05/17/2024 ms.subservice: admin ms.author: sericks ms.reviewer: sericks @@ -27,7 +27,7 @@ Make sure you have the System Administrator or System Customizer security role o **Check your security role** - Follow the steps in [View your user profile](/powerapps/user/view-your-user-profile). -- Don’t have the correct permissions? Contact your system administrator. +- Don't have the correct permissions? Contact your system administrator. > [!NOTE] > These settings might not yet be available in your environment. The settings availability depends on the region's release plan. @@ -63,8 +63,8 @@ Allow canvas editors to insert the Copilot answer component, which allows users | Setting | Description | Default value | |---------|-------------|---------------| |Power BI visualization embedding| More information: [Add or edit Power BI visualizations on your dashboard](/powerapps/user/add-powerbi-dashboards)| Off | -|Bing Maps| If **On**, Customer Engagement (on-premises) users will need to enter a Bing Maps key. Users don’t need to enter a key. | Off | -|Prevent social data in Dynamics | If you don’t want to receive social data in customer engagement apps (such as Dynamics 365 Sales and Customer Service), select **Off**. If you disable social engagement, your organization will not be able to receive social data in customer engagement apps (such as Dynamics 365 Sales and Customer Service). Users can continue to work with existing social data, however.| Off | +|Bing Maps| If **On**, Customer Engagement (on-premises) users will need to enter a Bing Maps key. Users don't need to enter a key. | Off | +|Prevent social data in Dynamics | If you don't want to receive social data in customer engagement apps (such as Dynamics 365 Sales and Customer Service), select **Off**. If you disable social engagement, your organization will not be able to receive social data in customer engagement apps (such as Dynamics 365 Sales and Customer Service). Users can continue to work with existing social data, however.| Off | ## Communications | Setting | Description | Default value | @@ -200,12 +200,12 @@ Allow canvas editors to insert the Copilot answer component, which allows users ## Disable empty address record creation |Setting |Description |Default value | |---------|---------|---------| -|Disable empty address record creation in Dataverse | When **On**, if the incoming payload does not have any address relevant data, an empty address data record will not be created. This feature is supported only for **Account** and **Contact** tables. | Off | +|Disable empty address record creation in Dataverse | When **On**, if the incoming payload does not have any address relevant data, an empty address data record will not be created. This feature is supported only for **Account** and **Contact** tables. More information: [Disable empty record creation](/power-apps/developer/data-platform/customer-entities-account-contact#disable-empty-record-creation) | Off | ## Enable deletion of address records |Setting |Description |Default value | |---------|---------|---------| -|Enable deletion of address records in Dataverse |When **On**, address records created in Dataverse for **Account** and **Contact** tables can be deleted through the user interface or through bulk deletion.| Off | +|Enable deletion of address records in Dataverse |When **On**, address records created in Dataverse for **Account** and **Contact** tables can be deleted through the user interface or through bulk deletion. More information: [Delete embedded address records](/power-apps/developer/data-platform/customer-entities-account-contact#delete-embedded-address-records)| Off | ## Power Apps ideas for canvas apps | Setting | Description | Default value | diff --git a/power-platform/developer/media/unified-experience/UnoEnvironmentUri.png b/power-platform/developer/media/unified-experience/UnoEnvironmentUri.png new file mode 100644 index 000000000..e371c8de2 Binary files /dev/null and b/power-platform/developer/media/unified-experience/UnoEnvironmentUri.png differ diff --git a/power-platform/developer/media/unified-experience/UnoLogin2.png b/power-platform/developer/media/unified-experience/UnoLogin2.png new file mode 100644 index 000000000..6f281f579 Binary files /dev/null and b/power-platform/developer/media/unified-experience/UnoLogin2.png differ diff --git a/power-platform/developer/media/unified-experience/UnoOption2.png b/power-platform/developer/media/unified-experience/UnoOption2.png new file mode 100644 index 000000000..d19efc35b Binary files /dev/null and b/power-platform/developer/media/unified-experience/UnoOption2.png differ diff --git a/power-platform/developer/unified-experience/finance-operations-install-config-tools.md b/power-platform/developer/unified-experience/finance-operations-install-config-tools.md index 417e9829c..51c3911bb 100644 --- a/power-platform/developer/unified-experience/finance-operations-install-config-tools.md +++ b/power-platform/developer/unified-experience/finance-operations-install-config-tools.md @@ -2,11 +2,13 @@ title: "Install and configure development tools (preview)" description: Set up required finance and operations app development tools on your local computer. author: pvillads -ms.date: 11/08/2023 +ms.date: 05/20/2024 ms.topic: how-to ms.reviewer: pehecke ms.author: pathaku ms.subservice: developer +contributors: + - Pankaj-Thakur --- # Install and configure development tools (preview) @@ -20,26 +22,44 @@ This article describes how to install and configure required Visual Studio finan > > The user account you'll be using for development in the sandbox environment must be assigned the System Administrator role. > -> The development machine running Microsoft Windows must have Visual Studio 2019 installed with at least the .NET desktop development workload and the Modeling SDK. This SDK can be selected under individual components in the Visual Studio installer. Refer to [required Visual Studio components](/dynamics365/fin-ops-core/dev-itpro/dev-tools/developer-tools-vs2017#required-visual-studio-components). The development machine also must have Microsoft SQL Server or SQL Server Express LocalDB installed. +> The development machine running Microsoft Windows must have Visual Studio 2022 installed with at least the .NET desktop development workload and the Modeling SDK. This SDK can be selected under individual components in the Visual Studio installer. Refer to [required Visual Studio components](/dynamics365/fin-ops-core/dev-itpro/dev-tools/developer-tools-vs2017#required-visual-studio-components). The development machine also must have Microsoft SQL Server or SQL Server Express LocalDB installed. ## Install the Power Platform extension for Visual Studio -Follow the instructions in this article to install the marketplace extension: [What is Power Platform Tools for Visual Studio](../devtools-vs.md). You don't need to install the plug-in profiler as directed in that article. +Follow the instructions in this article to install the extension from the marketplace: [What is Power Platform Tools for Visual Studio](../devtools-vs.md). You don't need to install the plug-in profiler as directed in that article. ### Connect to your online environment -After you have installed the Power Platform Tools extension for Visual Studio, follow these instructions to connect Visual Studio to your unified developer-focused environment. +After installing the Power Platform Tools extension for Visual Studio, follow these instructions to connect Visual Studio to your unified developer-focused environment. 1. Launch Visual Studio if not already running. -1. In the **Tools** menu, select **Connect to Dataverse** or **Download FinOps assets**. The former only downloads assets if not already downloaded once while the latter will download even if you had downloaded earlier. +1. In the **Tools** menu, select **Connect to Dataverse** or **Download Dynamics 365 FinOps assets**. + + - **Connect to Dataverse** only downloads assets if not downloaded earlier. + - **Download Dynamics 365 FinOps assets** always downloads. + 1. Select the desired options in the dialog and select **Login**. - Choose not to use the signed-in user if you need to use another account with a Visual Studio license. Enter the credentials as necessary to match your development user account. -1. When presented with a dialog to select a solution, select an available solution and then choose **Done**. -1. You will be presented with a list of Dataverse organizations (databases deployed). Find the sandbox environment created for online development and connect to it. - > [!NOTE] - > If you have only one online development environment, the organization list dialog may not be shown as you would automatically connect to the environment. - > :::image type="content" source="../media/unified-experience/UnoVSConnect.png" alt-text="Menu for connecting to unified environment from Visual Studio."::: - > :::image type="content" source="../media/unified-experience/UnoLogin.png" alt-text="Login dialog when connecting to unified environment from Visual Studio."::: + + If you need to use another account or a different online environment, don't choose to use the signed-in user. Enter the credentials for your developer user account with access to the online environment. + +1. Select an available solution in the dialog, and then choose **Done**. +1. Find the sandbox environment created for online development in the list of Dataverse environments and connect to it. + + > [!NOTE] + > If you have only one online development environment, the organization list dialog may not be shown as you would automatically connect to the environment. + > :::image type="content" source="../media/unified-experience/UnoVSConnect.png" alt-text="Menu for connecting to unified environment from Visual Studio."::: + > + > :::image type="content" source="../media/unified-experience/UnoLogin.png" alt-text="Login dialog when connecting to unified environment from Visual Studio with Show Advanced selected."::: + > + > If your account requires multi factor authentication, uncheck all checkboxes on login screen. + > + > If you are logging in to an online development environment in a tenant different from your own, where your user principal name (UPN) is added as a guest, update **Visual Studio** > **Tools** > **Options** > **Power Platform Tools** and select **Skip Discovery when connecting to Dataverse** and uncheck all the boxes on the login pane. You will be prompted to provide the Dataverse uri. + > + > :::image type="content" source="../media/unified-experience/UnoOption2.png" alt-text="Visual Studio> Tools> Options> Power Platform Tools to skip Discovery"::: + > + > :::image type="content" source="../media/unified-experience/UnoLogin2.png" alt-text="Login dialog when connecting to unified environment from Visual Studio."::: + > + > :::image type="content" source="../media/unified-experience/UnoEnvironmentUri.png" alt-text="Dialog to obtain the Dataverse uri to the unified development environment."::: ## Download and install the finance and operations extension and metadata @@ -50,76 +70,99 @@ After installing the Power Platform Tools extension and connecting to the online > [!IMPORTANT] > You can configure settings using the Visual Studio setting **Tools** > **Options** > **Power Platform Tools**. > -> Consider the option **Do not display Power Platform Explorer...** to speed up connecting to your environment and **Download logs...** to get logs for deployment and DBSync operations. +> The option **Auto setup for Dynamics 365...** is enabled by default. This ensures you do not have to manually extract system metadata or create the metadata configuration. The tool will do this for you. Do look into the Visual Studio output pane for any user action needed. +> +> Consider selecting the option **Do not display Power Platform Explorer...** to speed up connecting to your environment and **Download logs...** to get logs for deployment and DBSync operations. > > :::image type="content" source="../media/unified-experience/D365FinOpsToolsOptions.png" alt-text="Tools options"::: > > You need at least 12 GB of free space on the local system drive to download the extension and metadata. -Choose **OK** in the dialog to start the download. Visual studio notifies you once the download is completed. Visual Studio may not be responsive while downloading the assets, so please be patient. +Choose **OK** in the dialog to start the download. Visual Studio keeps you updated on the progress in the Visual Studio output pane. ### Extract system metadata +> [!NOTE] +> This is not required when auto setup is enabled + Downloaded assets can be found in the following location: `C:\Users\\AppData\Local\Microsoft\Dynamics365\` -Three files are downloaded and described below. +The following files are downloaded: -:::image type="content" source="../media/unified-experience/D365FinOpsAsetsDownloaded.png" alt-text="download asset files"::: +- `DYNAMICSXREFDB.bak` is a backup of the cross reference database. +- `Microsoft.Dynamics.Framework.Tools.Installer.vsix` is the Finance and operations extension. +- `PackagesLocalDirectory.zip` is the System metadata. +- `TraceParser.msi` [Learn more about Trace Parser](/dynamics365/fin-ops-core/dev-itpro/perf-test/trace-parser). -- Finance and operations extension is downloaded as Microsoft.Dynamics.Framework.Tools.Installer.vsix -- System metadata is downloaded as PackagesLocalDirectory.zip. -- Backup of the cross reference database as DYNAMICSXREFDB.bak - -Unblock any of the three files that needs unblocking. +Unblock any of the three files that need unblocking. :::image type="content" source="../media/unified-experience/D365FinOpsAsetsUnblock.png" alt-text="Unblock downloaded asset files"::: -Unpack the PackagesLocalDirectory.zip file as PackagesLocalDirectory. We recommend using the [7zip](https://www.7-zip.org/download.html) utility to speed up extraction. +Unpack the `PackagesLocalDirectory.zip` file as `PackagesLocalDirectory`. We recommend using the [7zip](https://www.7-zip.org/download.html) utility to speed up extraction. ### Install the finance and operations extension -Using Windows File Explorer, from the folder specified below, open the Microsoft.Dynamics.Framework.Tools.Installer.vsix file to install the extension. +> [!NOTE] +> This is only required when the Visual Studio output pane indicates it is. + +Using Windows File Explorer, from the folder specified below, open the `Microsoft.Dynamics.Framework.Tools.Installer.vsix` file to install the extension. + `C:\Users\\AppData\Local\Microsoft\Dynamics365\` -### Configure the finance and operations extension +### Configure the finance and operations extension + +> [!NOTE] +> This is not required when auto setup is enabled. To configure the extension, follow these instructions. 1. Start Visual Studio, and then select **Continue without code** from the dialog. -2. Navigate to **Extensions** > **Dynamics 365** > **Configure Metadata** for the first time. - If you do not see the **Configure Metadata** option, open **Extensions** > **Dynamics 365** > **Infolog** and retry. +1. Navigate to **Extensions** > **Dynamics 365** > **Configure Metadata** for the first time. + + If you don't see the **Configure Metadata** option, open **Extensions** > **Dynamics 365** > **Infolog** and retry. + :::image type="content" source="../media/unified-experience/D365FinOpsConfigureMetadataMenu.png" alt-text="Configure Metadata menu"::: -3. On the configuration form, select **New** and then create a new configuration. Refer to the field descriptions provided in the table that follows this procedure. - :::image type="content" source="../media/unified-experience/D365FinOpsConfigureMetadata.png" alt-text="Configure Metadata dialog"::: -4. Select **Save**. +1. On the configuration form, select **New** and then create a new configuration. Refer to the field descriptions provided in the [Configuration form field descriptions](#configuration-form-field-descriptions) table that follows this procedure. + + :::image type="content" source="../media/unified-experience/D365FinOpsConfigureMetadata.png" alt-text="Configure Metadata dialog"::: + +1. Select **Save**. + +#### Configuration form field descriptions | Form field | Description | |---|---| |Name| Name of the configuration you're creating now.| |Description| Description of the configuration you're creating now.| -|Cross reference database server| Set to "(localdb)\\." if you're using LocalDB, or "localhost" if you're using Microsoft SQL Server.| +|Cross reference database server| Set to `(localdb)\.` if you're using LocalDB, or `localhost` if you're using Microsoft SQL Server.| |Cross reference database name| The name for the cross reference database. The Visual Studio extension creates one if it doesn't exist.| -|Application version to restore cross reference database from| Please select this. It is populated from the assets downloaded when you connected to the unified developer environment.| +|Application version to restore cross reference database from| Select this. It's populated from the assets downloaded when you connected to the unified developer environment.| |Folder for your own custom metadata| Folder where your own code is (or will be).| |Folders for reference metadata| Should contain at least the path where you have the extracted the PackagesLocalDirectory folder mentioned in [Extract system metadata](#extract-system-metadata).| -If after filling in all the fields the **Save** button is still grayed out, you'll see error messages with a red border in tooltips on the offending fields. +#### Troubleshooting configuration + +If the **Save** button is still grayed out after filling in all the fields, you'll see error messages with a red border in tooltips on fields with invalid values. :::image type="content" source="../media/unified-experience/D365FinOpsConfigureMetadataValidation.png" alt-text="Configure Metadata Validation"::: -Ensure that you entered the correct value(s) for fields with errors. For example, use "(localdb)\\." if you're using LocalDB. -Also, if you're using LocalDB, you may need to first configure and test it. Consider issuing the following command from a Command prompt: `sqllocaldb create MSSQLLocalDB -s`. +Ensure that you entered the correct values for fields with errors. For example, use `(localdb)\.` if you're using LocalDB. +Also, if you're using LocalDB, you might need to first configure and test it. Consider issuing the following command from a Command prompt: + +`sqllocaldb create MSSQLLocalDB -s`. More information: [SQL Server Express LocalDB](/sql/database-engine/configure-windows/sql-server-express-localdb). > [!NOTE] > If the cross reference database does not already exist, the tool will restore the database from the backup downloaded to C:\Users\\``\AppData\Local\Microsoft\Dynamics365\\``. You'll see notifications in the Visual Studio **Output** pane. If you need to restore it again by yourself you can do so. For instructions to do a restore refer to [Restore to SQL Server](/sql/samples/adventureworks-install-configure?tabs=ssms#restore-to-sql-server). -After the configuration is saved, you may get a prompt for elevation as administrator to register the protocol handler and to extract compiler files. Go ahead and accept these prompts. +#### Completeing configuration + +After the configuration is saved, you might get a prompt for elevation as administrator to register the protocol handler and to extract compiler files. Go ahead and accept these prompts. -Once the configuration completes, navigate to **View** > **Application Explorer** . You should see the **Application Explorer** window open. You may have to restart Visual Studio first. +Once the configuration completes, navigate to **View** > **Application Explorer** . You should see the **Application Explorer** window open. You might have to restart Visual Studio first. :::image type="content" source="../media/unified-experience/D365FinOpsApplicationExplorer.png" alt-text="Application Explorer"::: @@ -127,7 +170,7 @@ You can create several configurations, but must select one to be current. The ch ## Summary -Congratulations! You’re now ready to build, deploy, debug, and test your X++ modules working with the Power Platform online development environment. Explore the possibilities with the power of finance and operations integrated with Power Platform. +Congratulations! You're now ready to build, deploy, debug, and test your X++ modules working with the Power Platform online development environment. Explore the possibilities with the power of finance and operations integrated with Power Platform. ## Next steps diff --git a/power-platform/guidance/adoption/secure-default-environment.md b/power-platform/guidance/adoption/secure-default-environment.md index a7656fcb8..24db22c6e 100644 --- a/power-platform/guidance/adoption/secure-default-environment.md +++ b/power-platform/guidance/adoption/secure-default-environment.md @@ -5,7 +5,7 @@ author: rranjit83 ms.author: rranjit ms.reviewer: matp ms.topic: how-to -ms.date: 04/11/2023 +ms.date: 05/17/2024 ms.custom: bap-template ms.subservice: guidance --- @@ -40,15 +40,25 @@ Add links to any other internal resources your makers might find helpful. ## Limit sharing with everyone -Makers can [share their apps](/power-apps/maker/canvas-apps/share-app) with other individual users, security groups, and, by default, everyone in the organization. You should consider using a gated process around widely used apps to enforce policies and requirements like these: +Makers can [share their apps](/power-apps/maker/canvas-apps/share-app) with other individual users and security groups. By default, sharing with your entire organization, or **Everyone**, is disabled. Consider using a gated process around widely used apps to enforce policies and requirements like these: - Security review policy - Business review policy - Application Lifecycle Management (ALM) requirements - User experience and branding requirements -Consider also disabling the **Share with Everyone** feature in Power Platform. With that restriction in place, only a small group of administrators may share an application with everyone in the environment. Here's how. +The **Share with Everyone** feature is disabled by default in Power Platform. We recommend you keep this setting disabled to limit the overexposure of canvas apps with unintended users. The **Everyone** group for your organization contains all users who have ever logged into your tenant, which includes guests and internal members. It's not just all internal employees within your tenant. Additionally, the membership of the **Everyone** group can't be edited nor viewed. To learn more about the **Everyone** group, go to /windows-server/identity/ad-ds/manage/understand-special-identities-groups#everyone. +If you would like to share with all internal employees or a large group of people, consider sharing with an existing security group of those members or creating a security group and sharing your app with that security group. + +When **Share with Everyone** is disabled, only a small group of administrators can share an application with everyone in the environment. If you're an administrator, you can run the following PowerShell command if you need to enable sharing with **Everyone**. + +1. First, open PowerShell as an administrator and log into your Power Apps account by running this command. + + ```powershell + Add-PowerAppsAccount + ``` + 1. Run the [Get-TenantSettings cmdlet](/powershell/module/microsoft.powerapps.administration.powershell/get-tenantsettings?view=pa-ps-latest&preserve-view=true) to get the list of your organization's tenant settings as an object. The `powerPlatform.PowerApps` object includes three flags: @@ -59,15 +69,17 @@ Consider also disabling the **Share with Everyone** feature in Power Platform. W ```powershell $settings=Get-TenantSettings - $settings.powerPlatform.powerApps.disableShareWithEveryone=$true + $settings.powerPlatform.powerApps.disableShareWithEveryone=$false ``` -1. Run the `Set-TenantSettings` cmdlet with the settings object to prevent makers from sharing their apps with everyone in the tenant. +1. Run the `Set-TenantSettings` cmdlet with the settings object to allow makers to share their apps with everyone in the tenant. ```powershell Set-TenantSettings $settings ``` + To disable sharing with **Everyone**, follow the same steps but `set $settings.powerPlatform.powerApps.disableShareWithEveryone = $true`. + ## Establish a data loss prevention policy Another way to secure the default environment is to [create a data loss prevention (DLP) policy](/power-platform/admin/create-dlp-policy) for it. Having a DLP policy in place is especially critical for the default environment because all employees in your organization have access to it. Here are some recommendations to help you enforce the policy. @@ -87,7 +99,7 @@ Use the following PowerShell cmdlets to customize the [governance policy message ### Block new connectors in the default environment -By default, all new connectors are placed in the Non-business group of your DLP policy. You can always [change the default group to either Business or Blocked](/power-platform/admin/prevent-data-loss#change-the-default-data-group). For a DLP policy that is applied to the default environment, we recommend that you configure the Blocked group as the default to make sure that new connectors remain unusable until they have been reviewed by one of your administrators. +By default, all new connectors are placed in the Nonbusiness group of your DLP policy. You can always [change the default group to either Business or Blocked](/power-platform/admin/prevent-data-loss#change-the-default-data-group). For a DLP policy that is applied to the default environment, we recommend that you configure the Blocked group as the default to make sure that new connectors remain unusable until they have been reviewed by one of your administrators. ### Limit makers to prebuilt connectors @@ -95,7 +107,7 @@ Restrict makers to only basic, nonblockable connectors to prevent access to the 1. Move all the connectors that can't be blocked to the business data group. -1. Move all the blockable connectors to the blocked data group. +1. Move all the connectors that can be blocked to the blocked data group. ### Limit custom connectors @@ -171,4 +183,4 @@ Power Platform tenant isolation is different from Microsoft Entra ID-wide tenant [Restrict cross-tenant inbound and outbound access (preview)](/power-platform/admin/cross-tenant-restrictions) -[Get-PowerAppTenantIsolationPolicy (Microsoft.PowerApps.Administration.PowerShell)](/powershell/module/microsoft.powerapps.administration.powershell/get-powerapptenantisolationpolicy?view=pa-ps-latest&preserve-view=true) \ No newline at end of file +[Get-PowerAppTenantIsolationPolicy (Microsoft.PowerApps.Administration.PowerShell)](/powershell/module/microsoft.powerapps.administration.powershell/get-powerapptenantisolationpolicy?view=pa-ps-latest&preserve-view=true)