Create webApplicationSegment

Namespace: microsoft.graph

Important

APIs under the /beta version in Microsoft Graph are subject to change. Use of these APIs in production applications is not supported. To determine whether an API is available in v1.0, use the Version selector.

Create a new webApplicationSegment object.

Permissions

Choose the permission or permissions marked as least privileged for this API. Use a higher privileged permission or permissions only if your app requires it. For details about delegated and application permissions, see Permission types. To learn more about these permissions, see the permissions reference.

Permission type	Least privileged permission	Higher privileged permissions
Delegated (work or school account)	Not supported.	Not supported.
Delegated (personal Microsoft account)	Not supported.	Not supported.
Application	Not supported.	Not supported.

Important

In delegated scenarios with work or school accounts, the signed-in user must be assigned a supported Microsoft Entra role or a custom role with a supported role permission. Application Administrator is the least privileged role supported for this operation. Cloud Application Administrator can't manage app proxy settings.

HTTP request

POST /applications/{applicationObjectId}/onPremisesPublishing/segmentsConfiguration/microsoft.graph.webSegmentConfiguration/applicationSegments

Request headers

Name	Description
Authorization	Bearer {token}. Required. Learn more about authentication and authorization.
Content-Type	application/json. Required.

Request body

In the request body, supply a JSON representation of the webApplicationSegment object.

You can specify the following properties when creating a webApplicationSegment.

Property	Type	Description
alternateUrl	String	Optional. If you're configuring a traffic manager in front of multiple app proxy application segments, this property contains the user-friendly URL that points to the traffic manager.
externalUrl	String	Required. The published external URL for the application segment; for example, https://intranet.contoso.com/.
internalUrl	String	Required. The internal URL of the application segment; for example, https://intranet/.
corsConfigurations	corsConfiguration_v2 collection	Optional. A collection of CORS Rule definitions for a particular application segment.

Response

If successful, this method returns a 204 No Content response code.

Examples

Request

The following example shows a request.

HTTP

POST https://graph.microsoft.com/beta/applications/2709c601-fcff-4010-94ea-5f862f755568/onPremisesPublishing/segmentsConfiguration/microsoft.graph.webSegmentConfiguration/applicationSegments/
Content-Type: application/json

{
    "externalUrl": "https://fe.contoso.com",
    "internalUrl": "https://be.contoso.com",
    "corsConfigurations": [
        {
            "resource": "/",
            "allowedOrigins": "*",
            "allowedHeaders": "*",
            "allowedMethods": "*",
            "maxAgeInSeconds": "3000"
        }
    ]
}

JavaScript

const options = {
	authProvider,
};

const client = Client.init(options);

const webApplicationSegment = {
    externalUrl: 'https://fe.contoso.com',
    internalUrl: 'https://be.contoso.com',
    corsConfigurations: [
        {
            resource: '/',
            allowedOrigins: '*',
            allowedHeaders: '*',
            allowedMethods: '*',
            maxAgeInSeconds: '3000'
        }
    ]
};

await client.api('/applications/2709c601-fcff-4010-94ea-5f862f755568/onPremisesPublishing/segmentsConfiguration/microsoft.graph.webSegmentConfiguration/applicationSegments/')
	.version('beta')
	.post(webApplicationSegment);

Important

Microsoft Graph SDKs use the v1.0 version of the API by default, and do not support all the types, properties, and APIs available in the beta version. For details about accessing the beta API with the SDK, see Use the Microsoft Graph SDKs with the beta API.

For details about how to add the SDK to your project and create an authProvider instance, see the SDK documentation.

Response

The following example shows the response.

HTTP/1.1 204 No Content