Inforiver
On-Prem Inforiver Writeback Matrix
On-Prem Inforiver Writeback Matrix
  • 👋Inforiver Writeback Matrix On-Prem
  • Before You Start
    • 🪄Basic Requirements
    • 🥌Entra ID App
    • 📧SMTP Service
    • 🕹️Inforiver Credentials
    • 📳Virtual Network (Optional)
  • Deployment
    • Microsoft Azure
      • Basics
      • Networking
      • SQL Database
      • Inforiver Workspace
      • SMTP
      • Final Deployment
    • Custom Visual Generation
    • Azure AD App Post Configuration
  • Architecture Concepts
    • Overview
    • O365 Permissions
    • External Connections
    • Azure Cost
  • Upgrade
    • Overview
    • Integrate Infobridge with Inforiver (for 2.x users)
    • Integrate EDITable with Inforiver (for 2.x users)
    • Update Inforiver Container Instances (for 3.x users)
    • Update EDITable Container Instance (for 3.x users)
    • Update Inforiver EDITable Container Instances (for 3.x users)
    • Update Inforiver EDITable Container Instances (for 4.x users)
  • How To Guides
    • Overview
    • Register Inforiver App with Certificate
    • Key Vault Integration
    • Custom Domain and SSL
    • Application Gateway Integration
    • Private App Service
    • Diagnostic Settings
    • Configuring Office 365 SMTP
    • Scaling Up Azure Database
    • Creation and Deletion of Database
    • Enabling App Service Logs
    • Scaling Up the App Service Plan
    • Scaling Redis Cache
    • Update Inforiver License
    • Update Azure AD Client & Other Environment Variables
    • Deploy Inforiver Writeback Matrix using Terraform
  • Troubleshooting Steps
    • Overview
    • Fix for SQL Bulk Load issue
Powered by GitBook
On this page
  1. How To Guides

Private App Service

PreviousApplication Gateway IntegrationNextDiagnostic Settings

Last updated 2 years ago

By default, the app service would be accessible from public network. But some organization would like to make this app service as private so that it would be accessible only from the local private network.

To make the app service follow the steps below.

  • Go to the Networking section of App service and select the option ‘Private Endpoints’

  • In the Private Endpoint connections page, click on ‘Add’ and select ‘Express’

  • Give a name for the endpoint and select the private subnet information from the dropdowns and make sure to keep the option Yes for Integrating with private DNS zone.

  • Once the Private Endpoint is created the public inbound IP will be replaced by a private IP and you may use this IP to map to a custom domain in your local DNS server or use the private FQDN (<appname>.azurewebsites.net) to access the app service within your extended private network.