Skip to content

Commit

Permalink
Merge pull request #7166 from MicrosoftDocs/main
Browse files Browse the repository at this point in the history
Publish main to live, 01/16/25, 3:30 PM PT
  • Loading branch information
Ruchika-mittal01 authored Jan 16, 2025
2 parents f1fc05f + f2713dc commit 9f828f0
Show file tree
Hide file tree
Showing 5 changed files with 36 additions and 43 deletions.
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
---
ms.date: 07/11/2018
ms.date: 01/16/2025
title: "Add and edit user profile properties in SharePoint"
ms.reviewer: waynewin
ms.author: ruihu
Expand Down Expand Up @@ -53,7 +53,7 @@ If your organization uses the cloud identity model, your user accounts are store
7. In the **Type** list, select the data type for the property.

> [!NOTE]
> If you select **string (Multi Value)**, the property will be permanently set as a multi-valued property. You cannot change this setting after you select **OK**. You can only delete the property and add it again as a new single-value property.
> If you select **string (Multi Value)**, the property will be permanently set as a multi-valued property. You can't change this setting after you select **OK**. You can only delete the property and add it again as a new single-value property.
8. If you selected binary, HTML, or string, use the **Length** box to enter the maximum number of characters allowed for property values.

Expand Down Expand Up @@ -98,7 +98,7 @@ If your organization uses the cloud identity model, your user accounts are store

## Synchronize custom properties

Custom properties from Active Directory or Microsoft Entra ID are not synchronized with SharePoint. For info about bulk updating custom user profile properties by using PowerShell, see [Call the import API from PowerShell](/sharepoint/dev/solution-guidance/bulk-user-profile-update-api-for-sharepoint-online#call-the-import-api-from-powershell).
Custom properties from Active Directory or Microsoft Entra ID aren't synchronized with SharePoint. For info about bulk updating custom user profile properties by using PowerShell, see [Call the import API from PowerShell](/sharepoint/dev/solution-guidance/bulk-user-profile-update-api-for-sharepoint-online#call-the-import-api-from-powershell).

## Need more help?

Expand Down
16 changes: 10 additions & 6 deletions SharePoint/SharePointOnline/hub-to-hub-association.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
---
ms.date: 09/11/2021
ms.date: 01/15/2025
title: "Associate a hub site to another hub site in the SharePoint admin center"
ms.reviewer:
ms.author: ruihu
Expand Down Expand Up @@ -63,12 +63,16 @@ The following diagram illustrates how hub sites can be associated to other hubs
![Image of the hub management panel in the SharePoint admin center](media/hub-settings-admin-2.png)

1. Go to <a href="https://go.microsoft.com/fwlink/?linkid=2185220" target="_blank">**Active sites** in the SharePoint admin center</a>, and sign in with an account that has [admin permissions](./sharepoint-admin-role.md) for your organization.
2. Select the hub site that you'd like to make an association. Then select **Hub** on the command bar and select **Edit hub site settings** to open to hub settings panel.
3. Next, select a hub to associate to in the **Parent hub association** field. Hubs that are available for association appears here.
4. To confirm which hubs have already been associated with your hub site, select **View child hubs associated to this hub**.
5. Select **Save**.
1. Select the hub site that you'd like to make an association. Then select **Hub** on the command bar and select **Edit hub site settings** to open to hub settings panel.
1. Next, select a hub to associate to in the **Parent hub association** field. Hubs that are available for association appears here.
1. To confirm which hubs have already been associated with your hub site, select **View hubs associated to this hub**.
1. Select **Save**.

> [!NOTE]
> Only a hub site that is a parent hub to other hub sites displays the link **View hubs associated to this hub**. If this link is missing, it means the hub site has no child hubs.
## Add links to hub associations to the hub site navigation

Hub site owners can quickly add links to the associated parent hub or child hubs when editing site navigation. Adding links to associated hubs is *optional* but makes it even easier for users to discover more relevant content across hubs.

![Image of the navigation section on a SharePoint site in edit mode](media/hub-nav-links.png)
Expand All @@ -91,7 +95,7 @@ Hub site owners can quickly add links to the associated parent hub or child hubs
## How to confirm the Parent hub association

To view the parent hub association, select **Settings** and then **Hub site settings**.
To view the parent hub association for a site, first go to the site, then select **Settings** and then **Hub site settings**.

> [!NOTE]
> Changes to hub associations must be made in the SharePoint admin center and require administrative privileges.
Expand Down
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
---
ms.date: 09/19/2020
ms.date: 01/15/2025
title: "Information architecture models and examples"
ms.reviewer:
ms.author: ruihu
Expand Down
17 changes: 7 additions & 10 deletions SharePoint/SharePointOnline/sharepoint-agents-azure-billing.md
Original file line number Diff line number Diff line change
Expand Up @@ -44,10 +44,9 @@ To set up SharePoint agents as an Azure resource, you need to do the following i

After setting up an Azure resource group for SharePoint agents, you can set up pay-as-you-go billing for SharePoint agents in the Microsoft 365 admin center. Here's how:

1. In the Microsoft 365 admin center, select [**Setup**](https://go.microsoft.com/fwlink/p/?linkid=2171997), and then view the **Billing and licenses** section.
1. Under **Billing and licenses**, select **Activate pay-as-you-go services**.
1. On the **Activate pay-as-you-go services** page, select **Get started**.
1. On the **Pay-as-you-go services** page, on the **Billing** tab, select **Agents in SharePoint**.
1. Go to the Microsoft 365 admin center, select **Settings** then **Org settings** then select **pay-as-you-go** services (formerly Microsoft Syntex).
Alternatively, you can select Setup, and then in the **Billing and licenses** section, select **Activate pay-as-you-go services**. On the **Activate pay-as-you-go services** page, select **Get started**.
1. On the **Pay-as-you-go services** page, under **Billing**, select **agents in SharePoint**.
1. On the **Set up billing and turn on services** panel, in the **Set up billing** section, under **Azure subscription**, select the dropdown, and then follow the steps to select the Azure subscription, resource group, and region. (The region determines where your tenant ID and usage information such as site names are stored.)
1. Read and accept the pay-as-you-go billing terms of service.
1. Select **Save**.
Expand All @@ -72,11 +71,9 @@ Your organization receives an invoice for all Azure services used at the end of

To Disconnect Agents from pay-as-you-go billing, follow these steps:

1. In the Microsoft 365 admin center, select [**Setup**](https://go.microsoft.com/fwlink/p/?linkid=2171997), and then view the **Billing and licenses** section.
1. Under **Billing and licenses**, select **Activate pay-as-you-go services**.
1. On the **Activate pay-as-you-go services** page, select **Get started**.
1. In the Microsoft 365 admin center, select **Settings** > **Org Settings**.
1. On the **Pay-as-you-go services** page, on the **Billing** tab, select **Agents in SharePoint**.
1. On the **Manage billing for agents in SharePoint** panel, under the Azure Subscription, select **Edit billing information**.
1. Select **Disconnect Azure subscription**.
1. On the **Manage billing** panel, under the Azure Subscription, select **Edit billing information**.
1. Select **Disconnect Azure subscription** under **Manage Billing**.
1. Select **Disconnect** within the **Disconnect Subscription** pop-up window.
1. View confirmation that your Azure Subscription has been disconnected Under **set up billing and turn on services**.
1. View confirmation that your Azure Subscription has been disconnected Under **set up billing and turn on services**.
38 changes: 15 additions & 23 deletions migration/mm-migration-admin-role.md
Original file line number Diff line number Diff line change
@@ -1,10 +1,10 @@
---
title: "Microsoft 365 Migration Admin role"
ms.reviewer:
ms.author: jtremper
author: JoanneHendrickson
ms.author: heidip
author: MicrosoftHeidi
manager: jtremper
ms.date: 01/25/2024
ms.date: 01/16/2025
recommendations: true
audience: ITPro
f1.keywords:
Expand All @@ -22,23 +22,17 @@ description: Learn about the admin role for Migration Manager

# Migration Admin role

>[!Note]
>This feature is currently in public preview, with full availability by June 2024.
A Microsoft 365 Migration Administrator role is now available to provide access to Migration Manager within the Microsoft 365 Admin Center. Currently, your migration team must be assigned the SharePoint admin role, giving more access than needed. With this new role, you limit usage to only what is required to migrate your content, reserving SharePoint Admin access to only users who need it.

>[!Important]
>This role doesn't allow access to Migration Manager from the SharePoint admin center. Continue to use the SharePoint Administrator role to migrate from network file shares.
In addition, this role provides all the functionality required to migrate including the ability to:

- Access Migration Manager to migrate from Google Drive, Dropbox, Box and Egnyte
- Select migration sources, create migration inventories (such as Google Drive user lists), schedule and execute migrations, and download reports
- Create new SharePoint sites if the destination sites don't already exist
- Create SharePoint lists under the SharePoint admin sites
- Create and update items in SharePoint lists
- Manage migration project settings and migration lifecycle for tasks
- Manage permission mappings from source to destination
- Access Migration Manager to migrate from file shares, Google Drive, Dropbox, Box, and Egnyte.
- Select migration sources, create migration inventories (such as Google Drive user lists), schedule and execute migrations, and download reports.
- Create new SharePoint sites if the destination sites don't already exist.
- Create SharePoint lists under the SharePoint admin sites.
- Create and update items in SharePoint lists.
- Manage migration project settings and migration lifecycle for tasks.
- Manage permission mappings from source to destination.

### How to use

Expand All @@ -53,17 +47,15 @@ To use this feature, assign the migration admin role to a new or existing user.
## FAQs

**Question:** I'm migrating network file shares. Can I use the Migration Admin role instead of the Sharepoint Admin?</br>
Answer: No. The Migration Admin role can be used only for our supported cloud migrations: Google Drive, Box, Dropbox, and Egnyte. This role is currently not supported for file share migrations. Continue to use accounts assigned the SharePoint Admin role.
Answer: Yes. You can sign in to the SharePoint Admin Center with the Migration Admin role and manage file share migration. Please note that when you install the file share migration agent, you need to sign in with the SharePoint Administrator role.

**Question:** Can I assign this role to an existing user account?</br>
Answer: Yes.

**Question:** I created a new user account in the Microsoft Admin Center, and assigned it the Migration Admin role. Does this new account have access existing projects?</br>
Answer: Yes, provided you access Migration Manager from the Microsoft Admin Center to migrate from Google Drive, Box, Dropbox and Egnyte.
</br>

**Question:** I currently have my migration team assigned with the SharePoint Admin role. Can I just continue using that?</br>
**Question:** I created a new user account in the Microsoft Admin Center, and assigned it the Migration Admin role. Does this new account have access to existing projects?</br>
Answer: Yes, provided you access Migration Manager from the Microsoft Admin Center to migrate from Google Drive, Box, Dropbox, and Egnyte.
</br>**Question:** I currently have my migration team assigned with the SharePoint Admin role. Can I just continue using that?</br>
Answer: Yes, using the Migration Admin role isn't required. However, it makes managing access easier.

**Question:** I see a gmail migration entry listed that I wasn't expecting.
**Question:** I see a Gmail migration entry listed that I wasn't expecting.
Answer: This is a known issue, and a fix is pending.

0 comments on commit 9f828f0

Please sign in to comment.