Molaprise Business Card App: Setup & Support Guide

This guide will walk you through deploying and using the Molaprise Business Card application, a solution for centralized, digital business card hosting.

I. Deployment (For Azure Administrator)

The Business Card App is deployed as an Azure Solution Template that places all resources within your Azure subscription.

A. Prerequisites

• Azure Subscription: You must have an active Azure subscription with Owner or Contributor rights to deploy the resources.

• Permissions: Global Administrator consent for the initial sign-in is required on first use (see Section II).

• Required Parameter: You will need the User Principal Names (UPNs) of the administrators who need access to the Branding/Admin page.

B. Deployment Steps

1. Find the Offer: Navigate to the Azure portal and search for “Molaprise Business Card App” in the Marketplace.

2. Start Deployment: Click “Create” to launch the Solution Template wizard.

3. Basic Settings:

   • Select your Subscription and a Resource Group for the deployment.

   • Choose an Azure Region.

4. Application Settings:

   • App Name (Required): Enter a unique name for your web application (e.g., molaprise-cards-us). This name will form the web app URL.

   • Admin UPNs (Required): Enter a comma-separated list of User Principal Names (emails) that should have access to the administrative Branding page (e.g., user1@yourdomain.com, admin@yourdomain.com).

5. Review and Create: The ARM template will automatically register the necessary redirect URIs with our multitenant application. Click “Review + Create” and then “Create” to start the deployment.

6. Access the App: Once deployment is complete (typically 5-10 minutes), navigate to the deployed Azure Web App resource in the portal and click the URL to open your new application.

II. First-Time Sign-In and Admin Consent

The application uses Microsoft Entra ID (formerly Azure AD) for all user authentication.

1. Initial Redirect: The first time any user (including the admin) visits the application, they will be redirected to the Microsoft Entra sign-in page.

2. Admin Consent (Crucial Step): Because the app is multi-tenant and requires access to user profile information (like job title) via the Microsoft Graph API, the first user to sign in must be a Global Administrator for your organization.

   • The Global Administrator will see an “Accept” button asking to grant Organization-wide Consent for the necessary permissions.

   • Clicking “Accept” ensures all subsequent users in your organization can sign in without seeing the consent prompt.

3. Sign-In: Once consent is granted, the user will be logged in and redirected to their personal business card profile page (the home page /).

III. Using the Application

A. The Home Page (Your Card)

The default home page (/) shows your personal business card based on your Azure AD profile information (name, title, email, phone) and your tenant’s branding settings.

B. The Admin Branding Page

• Access: Only users whose UPNs were listed in the Admin UPNs parameter during deployment can access this page: /admin/branding.

• Function: Use this page to set company-wide defaults:

  • Upload your Company Logo URL.

  • Set Company Name, Website, and Main Phone.

  • Define a default UPN Domain for public profile lookups.

C. Public Profile Sharing

The public-facing profile for a user is accessible via the URL: [YourAppURL]/profile/{alias}.

• Sharing: Users can share their QR code (available on the home page) or the direct URL.

• QR Code: The QR code on your profile links directly to your public profile page.

IV. Support and Troubleshooting