To get Appid , User token etc. Property value Click here.

To get the details about how to install App please go through below instruction.

1. Azure Portal

1.1  Create App Services

docImg1.png

For creating App Services click on “App Services” option. You will see the app service screen. Click on “+ ADD” to add new app service.

1.2  Add “Web App”

Select type “Web App” from list. Click create. Fill form and submit it.

docImg2.png
docImg3.png
docImg4.png

App Name : Descriptive name for your service Example: FMEmbedFeedService.

Subscription : Choose subscription available with your tenant.

Resource Group : A resource group is a collection of resources that share the same life cycle, permissions, and policies.

OS : Select Operating System Type.

App Service Plan/Location : The App Service plan settings will determine the location, features, cost and compute resources associated with your app.

Application Insights : Application Insights helps you detect and diagnose quality issues in your .NET web apps and web services, and enables you understand what your users actually do with it.

docImg5.png

1.3. Get Publish Profile

You can see list of services in which you can find your newly created service as above screen. Click on that service you will get redirected to service detailed page.

docImg6.png

Click on “Get publish profile” button and save it.

2. Visual Studio.

2.1 Get Client ID & Client Secret

In any browser address bar, type your site _layout/15 path and append “appregnew.aspx”.
Ex : https://contoso.sharepoint.com/sites/site1/_layouts/15/appregnew.aspx

docImg7.png

To get client ID and client secret, click “Generate” button and full fill rest of the details. Save this client id and client secret for furthers use.

Title : Descriptive name.

App Domain : Your azure tenant domain name. Example : virtualdeveloper.com

docImg8.png

Redirect URI : Once app will be launched on which page it should be redirected.
Example : https://www.contoso.com/Default.aspx

2.2 AppManifest.xml & Web.config file

Set the SharePoint client id and client secret under “<appSettings>” tag in web.config file and only client id in appmanifest.xml.

Web.config

docImg9.png

AppManifest.xml

docImg10.png

2.3 SharePoint Project

docImg11.png

Right click on SharePoint project and select “Publish” option.

2.4 Edit Current Profile

docImg12.png

2.5 2.5. Publish Office and SharePoint Add-ins

docImg13.png

Set SharePoint client id and client secret and finish. Generated in generate in step 2.1.

2.6. Deploy Project

docImg14.png

Click on “Deploy your web project” button.

2.7 Import Profile

docImg15.png

2.8 2.8. Import publish profile

docImg16.png

Import profile you saved earlier in the step 1.6.

  • Just browse the “publish profile
  • Click on “Validate Connection” button for validation n checking.
  • Click on “preview” button if you want to see a preview.
  • Click on “Publish” button.

2.1 Publish Successfully.

docImg17.png

You will be notified when it will be got completed.

2.2 Package Files

docImg18.png

Get app package files “. app file”.

3. SharePoint

3.1 App Catalog

Open App Catalog site of tenant and upload app package file generated in step 2.10.

docImg19.png

3.2  Add app in SharePoint Site

Go to Site contents > “Add an app”.

docImg20.png

Choose App “FM Embed” and then trust it.

docImg21.png

3.3 Add app on Page

  1. Open Site Page.
  2. Edit Page.
  3. Select “insert” tab from top ribbon.
  4. Click “AppPart
docImg22.png

5. Select “WorkPlaceFeedAppPart”. Click “Add”.

docImg23.png

2.1 Set Property of App part

1. Edit the Web Part

2. Select the custom property

docImg24.png

3. Set property value. To check how to get value of Email, GroupId, UserToken refer click here.

3.6 App Output

docImg25.png

Note : Above all steps are required to do to setup in new tenant. It is for those customers who are buying from you directly and need separate tenant hosting.

To Get App from Seller Dashboard Directly :

Go to Site Contents > Add an app > SharePoint Store > Get FM Embed then follow all the steps from 3.3 mentioned earlier.

docImg26.png