Merging changes synced from https://github.com/MicrosoftDocs/powerbi-…

…docs-pr (branch live)

powerbi-docs/enterprise/service-admin-azure-ad-b2b.md

@@ -26,15 +26,15 @@ This article provides a basic introduction to Microsoft Entra B2B in Power BI. F
 Make sure you enable the [Invite external users to your organization](/fabric/admin/service-admin-portal-export-sharing) feature in the Power BI admin portal before inviting guest users. Even when this option is enabled, the user must be granted the Guest Inviter role in Microsoft Entra ID to invite guest users.  
 
 > [!NOTE]
-> The [Invite external users to your organization](/fabric/admin/service-admin-portal-export-sharing) setting controls whether Power BI allows inviting external users to your organization. After an external user accepts the invite, they become a Microsoft Entra B2B guest user in your organization. They appear in people pickers throughout the Power BI experience. If the setting is disabled, existing guest users in your organization continue to have access to any items they already had access to and continue to be listed in people picker experiences. Additionally, if guests are added through the [planned invite](#planned-invites) approach they will also appear in people pickers. To prevent guest users from accessing Power BI, use a Microsoft Entra Conditional Access policy.
+> The [Invite external users to your organization](/fabric/admin/service-admin-portal-export-sharing) setting controls whether Power BI allows inviting external users to your organization. After an external user accepts the invite, they become a Microsoft Entra B2B guest user in your organization. They appear in people pickers throughout the Power BI experience. If the setting is disabled, existing guest users in your organization continue to have access to any items they already had access to and continue to be listed in people picker experiences. Additionally, if guests are added through the [planned invite](#planned-invites) approach they'll also appear in people pickers. To prevent guest users from accessing Power BI, use a Microsoft Entra Conditional Access policy.
 
 ## Who can you invite?
 
 Most email addresses are supported for guest user invitations, including personal email accounts like gmail.com, outlook.com, and hotmail.com. Microsoft Entra B2B calls these addresses *social identities*.
 
 > [!NOTE]
 > In Microsoft Entra ID, external users can be set to UserType Member. In Power BI, support for UserType Member is currently in preview. Note the following:
-> * Microsoft Purview Information Protection is not supported for external members. Admins in the provider tenant are advised not to enable information protection for external members.
+> * Microsoft Purview Information Protection isn't supported for external members. Admins in the provider tenant are advised not to enable information protection for external members.
 >
 > In some situations, external members may see errors during their first sign-in attempt on the provider tenant. To unblock these external members, grant them permission to a Power BI item, such as a workspace, semantic model, or report, and then have them sign in again.
 
@@ -128,7 +128,7 @@ The following table lists the licensing requirements for B2B access to Power BI.
 > Pro Trial users can't invite guest users in Power BI. 
 
 ### Steps to address licensing requirements
-As noted above, the guest user must have the proper licensing in place to view the content that you shared. There are a few ways to make sure the user has a proper license: 
+As noted previously, the guest user must have the proper licensing in place to view the content that you shared. There are a few ways to make sure the user has a proper license: 
 * Use Power BI Premium capacity.
 * Assign a Power BI Pro or a Premium Per User (PPU) license.
 * Use a guest's Power BI Pro or PPU license.
@@ -174,7 +174,7 @@ There are some limitations to the B2B experience that you should be aware of:
 
 * On the Home page, the “From external orgs” tab won't list content shared from other clouds.
 
-* Cross-cloud sharing does not work when sharing with a security group. For instance, if a user using Power BI in a national cloud invites a security group from the public cloud or vice versa, access is not granted. This is because the service can't resolve the members of these groups across clouds.
+* Cross-cloud sharing doesn't work when sharing with a security group. For instance, if a user using Power BI in a national cloud invites a security group from the public cloud or vice versa, access isn't granted. This is because the service can't resolve the members of these groups across clouds.
 
 ## Admin Info for B2B Collaboration 
 
@@ -195,10 +195,7 @@ Additionally, to use in-place semantic model sharing, tenant admins need to enab
 
 ## Considerations and Limitations
 
-* Information protection in Power BI doesn't support B2B and multi-tenant scenarios. This means that although external users may be able to see sensitivity labels in Power BI:
-    * They can't set labels
-    * [Mandatory](/fabric/governance/service-security-sensitivity-label-mandatory-label-policy) and [default label](/fabric/governance/service-security-sensitivity-label-default-label-policy) polices won't be enforced for them
-    * While they can view a report that has a label with protection settings, if they export data from that report to a file, they may not be able to open the file, as it has the Microsoft Entra permissions of the original organization that it got due to the label on the report.
+* Information protection: See [Sensitivity labels in Fabric and Power BI: Considerations and limitations](./service-security-sensitivity-label-overview.md#considerations-and-limitations).
 
 * Some experiences aren't available to guest users even when they have higher-level permissions. To update or publish reports, guest users need to use the Power BI service, including Get Data, to upload Power BI Desktop files. The following experiences aren't supported:
   * Direct publishing from Power BI desktop to the Power BI service
@@ -210,7 +207,7 @@ Additionally, to use in-place semantic model sharing, tenant admins need to enab
   * Guest users can't be @mentioned in commenting
   * Guest users who use this capability should have a work or school account
 
-* Guest users using social identities will experience more limitations because of sign-in restrictions.
+* Guest users using social identities experience more limitations because of sign-in restrictions.
   * They can use consumption experiences in the Power BI service through a web browser
   * They can't use the Power BI Mobile apps
   * They won't be able to sign in where a work or school account is required

powerbi-docs/transform-model/service-semantic-model-version-history.md

@@ -112,7 +112,7 @@ You can monitor the effect restoring to a previous version with version history
 |---------|---------|---------|---------|
 |Web Modeling write     |A data model write operation in the semantic model web modeling user experience         |Semantic models|Interactive         |
 
-
+There is no additional charge for the storage used to capture versions in the semantic model version history for your models.
 
 ## Requirements and permissions
 
@@ -133,6 +133,7 @@ Semantic model version history is currently in preview. Keep the following in mi
 * Semantic model version history is subjected to the same limitations as [editing data models in the Power BI service](service-edit-data-models.md). 
 * Version history won't be captured for semantic models that haven't yet upgraded to [enhanced metadata format](../connect-data/desktop-enhanced-dataset-metadata.md). Additionally, if a model with the old metadata format is published over a model in the enhanced metadata format, all previously captured semantic model versions for that model will be deleted.
 * Moving a model between capacities will delete its version history.
+* You can't access versions in semantic model version history outside of the version history pane on the web. For full source control with greater flexibility and support for more versions, use [git integration](/fabric/cicd/git-integration/git-get-started), which can be used in combination with version history for the same semantic model. 
 * The data in your semantic model may become outdated after restoring to a previous version. To ensure you have the most recent data, complete a refresh after performing a restore. Refresh behavior may vary across storage modes. For example, Direct Lake models with [automatic updates](/fabric/get-started/direct-lake-overview#automatic-updates) configured will automatically update with the most recent data after a restore, without requiring you to manually initiate a refresh.
 * The semantic model must have [large semantic model storage format enabled](../enterprise/service-premium-large-models.md). Semantic models are automatically converted to large semantic model storage format the first time they're opened in Editing mode in the web or when opening a [Direct Lake model for live editing in Desktop](/fabric/get-started/direct-lake-power-bi-desktop#live-edit-a-semantic-model-in-direct-lake-mode). If a semantic model with versions captured in version history has the large semantic model storage format disabled in the model settings, all version history for this model will be deleted. A warning in the semantic model settings will notify you of this impact before you make the change:
   :::image type="content" source="media/service-semantic-model-version-history/service-semantic-model-version-history-12.png" alt-text="Screenshot showing a warning about deleting version history.":::