Skip to content

Commit

Permalink
Merge pull request #12309 from MicrosoftDocs/main
Browse files Browse the repository at this point in the history
9/03/2024 PM Publish
  • Loading branch information
Emma-yxf authored Sep 3, 2024
2 parents 1fbe0f7 + 975dcac commit aa6aba0
Show file tree
Hide file tree
Showing 3 changed files with 12 additions and 14 deletions.
2 changes: 1 addition & 1 deletion .openpublishing.redirection.json
Original file line number Diff line number Diff line change
Expand Up @@ -5663,7 +5663,7 @@
},
{
"source_path": "powerbi-docs/admin/service-admin-portal-capacity-settings.md",
"redirect_url": "/fabric/admin/service-admin-portal-capacity-settings",
"redirect_url": "/fabric/admin/capacity-settings",
"redirect_document_id": false
},
{
Expand Down
4 changes: 2 additions & 2 deletions powerbi-docs/developer/embedded/azure-pbie-create-capacity.md
Original file line number Diff line number Diff line change
Expand Up @@ -50,8 +50,8 @@ Before creating a Power BI Embedded capacity, make sure you're signed into Power
* **Subscription** - The subscription you would like to create the capacity against.

* **Resource group** - The resource group that contains this new capacity. Pick from an existing resource group, or create another. For more information, see [Azure Resource Manager overview](/azure/azure-resource-manager/resource-group-overview).

* **Resource name** - The resource name of the capacity.
* **Resource name** - The resource name of the capacity. Please note that capacity name must be unique within the same region and must start with a letter and have 3 to 63 lowercase letters or numbers.

* **Location** - The location where Power BI is hosted for your tenant. Your default location is your home region, but you can change the location using [Multi-Geo options](embedded-multi-geo.md).

Expand Down
20 changes: 9 additions & 11 deletions powerbi-docs/enterprise/service-premium-backup-restore-dataset.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ ms.reviewer: ''
ms.service: powerbi
ms.subservice: powerbi-premium
ms.topic: conceptual
ms.date: 05/31/2024
ms.date: 07/25/2024
LocalizationGroup: Premium
---

Expand Down Expand Up @@ -69,9 +69,14 @@ When using the **Backup and Restore** feature with Power BI, keep the following
* Power BI must be able to access your ADLS Gen2 directly. Your ADLS Gen2 can't be located in a VNET and the firewall can't be turned on.

* If your ADLS Gen2 is already working with **Backup and Restore**, and you disconnect and later reconfigure it to work with **Backup and Restore** again. You must first rename or move the previous backup folder, or the attempt will result in errors and failure.

* **Restore** only supports restoring the database as a **Large Model (Premium)** database.

* Only **enhanced format model (V3 model)** is allowed to be restored.
* There's a new property, `ignoreIncompatibilities`, for the `restore` command that addresses Row-level security (RLS) incompatibilities between Azure Analysis Services (AAS) and Power BI Premium. Power BI Premium only supports the read permission for roles, but AAS supports all permissions. If you try to restore a backup file for which some roles don't have *read* permissions, you must specify the `ignoreIncompatibilities` property in the `restore` command. If not specified, restore can fail. When specified, the role without the *read* permission is dropped. Currently, there's no setting in SSMS that supports the `ignoreIncompatibilities` property, however, you can specify it in a `restore` command using Tabular Model Scripting Language (TMSL). For example:

* When access to account key on your storage account is [disabled](/azure/storage/common/shared-key-authorization-prevent#disable-shared-key-authorization), you might get this error: *Key based authentication is not permitted on this storage account*.

* The property, `ignoreIncompatibilities` for the `restore` command addresses Row-level security (RLS) incompatibilities between Azure Analysis Services (AAS) and Power BI Premium. Power BI Premium only supports the read permission for roles, but AAS supports all permissions. If you try to restore a backup file for which some roles don't have *read* permissions, you must specify the `ignoreIncompatibilities` property in the `restore` command. If not specified, restore can fail. When specified, the role without the *read* permission is dropped. Currently, there's no setting in SSMS that supports the `ignoreIncompatibilities` property, however, you can specify it in a `restore` command using Tabular Model Scripting Language (TMSL). For example:

```json
{
Expand Down Expand Up @@ -115,15 +120,8 @@ When using the **Backup and Restore** feature with Power BI, keep the following

## Related content

* [What is Power BI Premium?](service-premium-what-is.md)
* [SQL Server Management Studio (SSMS)](/sql/ssms/download-sql-server-management-studio-ssms)
* [Analysis Services cmdlets for PowerShell](https://www.powershellgallery.com/packages/Az.AnalysisServices)
* [Semantic model connectivity with the XMLA endpoint](service-premium-connect-tools.md)
* [Using Autoscale with Power BI Premium](service-premium-auto-scale.md)
* [Power BI Premium FAQ](service-premium-faq.yml)
* [Power BI Premium Per User FAQ](service-premium-per-user-faq.yml)
* [Add or change Azure subscription administrators](/azure/cost-management-billing/manage/add-change-subscription-administrator)
* [Configuring tenant and workspace storage](../transform-model/dataflows/dataflows-azure-data-lake-storage-integration.md)

More questions? [Ask the Power BI Community](https://community.powerbi.com/).
* [Semantic model connectivity with the XMLA endpoint](service-premium-connect-tools.md)

* [Configuring tenant and workspace storage](../transform-model/dataflows/dataflows-azure-data-lake-storage-integration.md)

0 comments on commit aa6aba0

Please sign in to comment.