Configure Manufacturing data solutions resource using Azure portal

This section provides information on what changes or updates are needed after deploying Manufacturing data solutions in the designated tenant.

Assign permission in Fabric to the identity of the ingestion application

Manufacturing data solutions contains an Azure Function App resource responsible for ingesting both streaming and batch data. This Azure Function is residing inside the resource group MDS-{your-deployment-name}-MRG-{UniqueID}.

• For ingesting streaming data, you can use a connection string to the Fabric Event Hubs namespace.

• For ingesting batch data, you can use the service principal (Managed Identity) of the Function App. This identity needs to have permission to Fabric.

1. Download the file fn-auth-lakehouse.ps1 to your local system. This file can be used for ingesting data.

2. Start PowerShell as an administrator.

3. Run the command Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass. This ensures the script can be run in this process only.

4. Navigate to the folder where the downloaded file is located.

5. Invoke the script with the correct arguments.

   .\fn-auth-lakehouse.ps1 -FunctionAppIdentity "<FunctionAppObjectId>" -WorkspaceName "<OneLakeWorkspace>" -TenantId <TenantId> For example .\fn-auth-lakehouse.ps1 -FunctionAppIdentity "00001111-aaaa-2222-bbbb-3333cccc4444" -WorkspaceName "mdscontoso" -TenantId "aaaabbbb-0000-cccc-1111-dddd2222eeee" The FunctionAppObjectId can be found by navigating to the Manufacturing data solutions resource group in Azure, search for the Function App with a name resembling fn-mci4m-xxxxxxxx-processor, navigate to this Function App, and move to the Identity blade. The Object ID should be visible on this page.

   

   After the script is executed, connection between the Onelake workspace and the Function App is created. Now under Manage access in Onelake workspace you can find the Function App.

   

   Note

   Service principals, like managed identities, can only be added when both Microsoft Fabric and Microsoft Azure are located within the same tenant and use the same Entra ID.

Update Manufacturing data solutions resource using Azure portal

After your deployment is complete, you can update the properties of your deployment like version, SKU, copilot configuration, managed identity, and Fabric configuration.

Version update

Choose the version you want and select Submit to update your Manufacturing data solutions instance.

Agent configuration

You can switch between your own Azure OpenAI resource or Manufacturing data solutions managed Azure OpenAI deployment. You can also configure GPT Model name, GPT Model version, and GPT Model capacity for the GPT model. For Embeddings model only model, capacity can be changed.

Managed Identity

You can add or change the current managed identity if necessary.

Fabric configuration

You can update both OneLake and Key Vault configurations.

SKU

In the Manufacturing data solutions Deployment details, select SKU > Update, and then select the desired SKU.

Deny Assignment Settings

Use this setting only in critical situations when unblocking is needed, such as for S360 issues or vulnerability management, and additional access is required for underlying resources like AKS. Use this setting sparingly as it grants elevated permissions. Don't delete a resource. AKS access is subject to intersection with the AKS Admin Group ID. It's recommended to contact support before using this setting.

To use this setting, in Deployment details, select Deny Assignment Settings and select Add. Then, specify a Group Object ID. Deny assignments don't apply to this group.

Assign manufacturing user roles

There are two roles available on Manufacturing data solutions:

Details on which endpoints require what roles can be found in the [OpenAPI specificationsfor the version deployed]. App roles reside in App Registration.

You need to assign certain roles to all testers and users of the sample apps.

1. Go to Microsoft Entra ID > App Registrations.

2. Select the app registration with your chosen app name.

   

3. Select Go to Enterprise Application.

4. Select Assign users and groups.

5. Select Add user/group and then select the user and assign the desired role.

   

Run a health check

It's best to call the Health Check API to validate the success of both the deployment and user role configurations. The Health Check API returns the health of Manufacturing data solutions and whether it's ready to process requests. You need to have the Manufacturing Admin role for validating the authentication.

Generate an authentication token

You need a valid authentication token in the request header when calling a Manufacturing data solutions API. Here are two examples of how to generate this token:

Connect-AzAccount -Tenant YOUR_TENANT_ID
$ACCESS_TOKEN = (Get-AzAccessToken -ResourceUrl "api://{Entra Application Id}").Token

az login --tenant YOUR_TENANT_ID
ACCESS_TOKEN=$(az account get-access-token --resource api://{Entra Application Id} --query accessToken --output tsv)

Since Manufacturing data solutions service uses the Managed-On Behalf Of (MOBO) model, when you create a Manufacturing data solutions resource, all the needed resources by Manufacturing data solutions service are created in the customer's subscription.

Get the Manufacturing data solutions Service URL

You need the Manufacturing data solutions Service URL when constructing the URL for Manufacturing data solutions API calls. You can get it from Service URL from the screenshot given:

Run GET https://{serviceUrl}/mds/service/health, making sure to pass in the authentication token in the header.

Here are two examples of how to make this call:

      Invoke-RestMethod -Uri "https://{serviceUrl}/mds/service/health" -Method Get -Headers @{ Authorization = "Bearer $ACCESS_TOKEN" }

     az rest --method get --url https://$serviceUrl/mds/service/health --headers "Authorization=Bearer $ACCESS_TOKEN"

The response codes should be one of the given values:

Upload sample data (optional)

Manufacturing data solutions initially contains no data. The steps to upload the Bakery Shop sample dataset are as follows:

1. Download and extract files transformed.zip.

2. Navigate to the Power BI portal

3. Select your Fabric workspace and your Fabric Lakehouse.

4. Select the Files folder, and subfolder if you specified one during the deployment.

5. Select ... > Upload > Upload files.

6. Select all the CSV files in the top-level folder and then Upload.

7. Select Open > Upload folder.

8. Select the mapping folder and then Upload.