Publishing & Sharing Your Power App

By Ashwin Venugopal -

 






Introduction

When your Power App is ready, use the save, publish and share icons. Your workflow for publishing for the first time would be:

  1. Build your app
  2. Save your changes
  3. Click Publish (to make this the version that people will use)
  4. Share (select who can access the app or view it)
  5. A final step to take if you have linked your app to data is to make sure the data is also shared with your intended group or person.

After completing this step, people will have the opportunity to engage with and utilize the app you have developed. An important tip is to choose a descriptive name, design an appealing icon, and provide a brief overview in the description.

Power Apps Mobile App

In order to use a Power App that you have developed on your mobile device, you must download the Power Apps app from the Google Play Store (for Android devices) or the Apple App Store (for iOS devices).

The first time you start the Power Apps app, it will ask you to sign into your organizational account. When this is done, all apps that you created, or which have been shared with you will be displayed. If you have a couple of apps that you use frequently you can favourite them. You can also set an app to load automatically when you open the Power Apps Mobile app.

Licensing of Power Apps

Within the Microsoft Cloud ecosystem, licensing varies greatly and is always changing, so it's worthwhile to do some study.

One thing to focus on is the minimum level that you may need. For example, if your business is 3 people all wanting to share news items together, you can most likely get by on a licence which cost less than $20 per month. However, if you are looking to roll out an enterprise-wide security check-in solution which integrates with the Dataverse for secure permission sharing and scale, you will be looking at an entirely different level of licence. There are experts in the marketplace to ask for advice and many communities.

Conclusion

We have successfully learnt about publishing and sharing of Power App. 




















Comments

Post a Comment

Popular posts from this blog

Information Protection Scanner: Resolve Issues with Information Protection Scanner Deployment

By Ashwin Venugopal -
Image
  About If you are experiencing problems with the Microsoft Purview Information Protection scanner, check the health of your deployment by utilizing the Start-ScannerDiagnosticsPowerShell cmdlet to start the scanner diagnostic tool. The diagnostics tool checks the following details and then creates a log files with the results: Whether the database is up to date. Whether network URLs are accessible. Whether there's a valid authentication token and policy can be acquired. Whether the profile is defined in the Azure portal. Whether offline/online configuration exists and can be acquired. Whether the rules configured are valid.  The Start-ScannerDiagnostics command does not perform a comprehensive check of prerequisites. If you encounter problems with the scanner, you need to verify that your system meets the scanner's requirements, and that your scanner's configuration and installation are finished.  Verify Scanning Details Per Scanner Node and Repository Run the Get-ScanSt...
Read more

How AMI Store & Restore Works?

By Ashwin Venugopal -
Image
  CreateStoreImageTask The CreateStoreImageTask API stores an AMI as a single object in an S3 bucket. The API initiates a task that collects all the data from the AMI and its associated snapshots, subsequently using an S3 multipart upload to store this data in an S3 object. It gathers all elements of the AMI, including most of the non-Region-specific metadata and all EBS snapshots included in the AMI, and consolidates them into a single object in S3. During the upload process, the data is compressed to minimize the space utilized in S3, which means that the S3 object could be smaller than the total sizes of the snapshots in the AMI. If the account making this API call has access to AMI and snapshot tags, they will be retained. The S3 object shares the same ID as the AMI, except it has a .bin extension. Additionally, the S3 metadata tags for the object include the AMI name, AMI description, AMI registration date, AMI owner account, and a timestamp indicating when the store operation...
Read more

Create A Store Image Task

By Ashwin Venugopal -
Image
  Introduction When you save an AMI in an S3 bucket, a task for storing the image is initiated. This store image task allows you to track the progress and result of the procedure. Securing your AMIs It is crucial to verify that the S3 bucket is set up with adequate security to protect the content of the AMI and that this security is upheld for the entire duration that the AMI objects are stored in the bucket. If this cannot be achieved, it is advisable to refrain from using these APIs. Make sure that public access to the S3 bucket is prohibited. It is suggested to activate Server-side encryption for the S3 buckets where you keep the AMIs, even though it’s not mandatory. When AMI snapshots are transferred to the S3 object, they are sent over TLS connections. It is possible to save AMIs that contain encrypted snapshots; however, the snapshots will be decrypted during the storing process. Identify the source AMI used to create a new Amazon EC2 AMI You can determine the AMI that was us...
Read more