Skip to content

Commit c116d54

Browse files
authored
Merge pull request #293322 from MicrosoftDocs/repo_sync_working_branch
Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)
2 parents f6529cd + 9ed9698 commit c116d54

File tree

4 files changed

+10
-2
lines changed

4 files changed

+10
-2
lines changed

articles/azure-functions/run-functions-from-deployment-package.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -53,6 +53,7 @@ The following table indicates the recommended `WEBSITE_RUN_FROM_PACKAGE` values
5353
+ When deploying your function app to Windows, you should set `WEBSITE_RUN_FROM_PACKAGE` to `1` and publish with zip deployment.
5454
+ When you run from a package, the `wwwroot` folder is read-only and you receive an error if you write files to this directory. Files are also read-only in the Azure portal.
5555
+ The maximum size for a deployment package file is 1 GB.
56+
+ The deployment uses temporary storage when unpacking your project files. This means that your function app must have enough available temporary storage space to hold the contents of your package. Keep in mind that the temporary storage limit for a Consumption plan is [500 MB per plan](functions-scale.md#service-limits). To learn about how to troubleshoot issues with temporary storage, see [How to troubleshoot temporary storage on Azure App Service](/troubleshoot/azure/app-service/temporary-storage-for-azure-app-service).
5657
+ You can't use the local cache when running from a deployment package.
5758
+ If your project needs to use remote build, don't use the `WEBSITE_RUN_FROM_PACKAGE` app setting. Instead, add the `SCM_DO_BUILD_DURING_DEPLOYMENT=true` deployment customization app setting. For Linux, also add the `ENABLE_ORYX_BUILD=true` setting. For more information, see [Remote build](functions-deployment-technologies.md#remote-build).
5859

articles/expressroute/expressroute-faqs.md

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -266,6 +266,13 @@ No. From a routing perspective, all virtual networks linked to the same ExpressR
266266

267267
Yes. You can link a single virtual network with up to four ExpressRoute circuits in the same location or up to 16 ExpressRoute circuits in different peering locations.
268268

269+
### Service Endpoint Policy on the Gateway Subnet?
270+
271+
Configuring a Service Endpoint Policy (SEP) on the Gateway Subnet is not advisable due to potential issues, including:
272+
* Failures in gateway service deployment
273+
* Challenges with scaling and service healing
274+
275+
269276
### Do virtual networks connected to ExpressRoute circuits have Internet connectivity?
270277

271278
Yes. If a default routes (0.0.0.0/0) or Internet route prefixes isn't advertised through the BGP session, you can connect to the Internet from a virtual network linked to an ExpressRoute circuit.

articles/iot/iot-mqtt-connect-to-iot-hub.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -189,7 +189,7 @@ For more information about using MQTT with modules, see [Publish and subscribe w
189189

190190
The [IoT MQTT Sample repository](https://github.com/Azure-Samples/IoTMQTTSample) contains C/C++, Python, and CLI samples that show you how to send telemetry messages, receive cloud-to-device messages, and use device twins without using the Azure device SDKs.
191191

192-
The C/C++ samples use the [Eclipse Mosquitto](https://mosquitto.org) library, the Python sample uses [Eclipse Paho](https://www.eclipse.org/paho/), and the CLI samples use `mosquitto_pub`.
192+
The C/C++ samples use the [Eclipse Mosquitto](https://mosquitto.org) library, the Python sample uses [Eclipse Paho](https://projects.eclipse.org/projects/iot.paho), and the CLI samples use `mosquitto_pub`.
193193

194194
To learn more, see [Tutorial - Use MQTT to develop an IoT device client](./tutorial-use-mqtt.md).
195195

articles/notification-hubs/firebase-migration-rest.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -186,7 +186,7 @@ If you have an existing GCM registration, update the registration to **FcmV1Regi
186186
</entry>
187187
```
188188

189-
#### Option 2: Create FCM c1 installation or update GCM installation to FCM v1
189+
#### Option 2: Create FCM V1 installation or update GCM installation to FCM v1
190190

191191
See [Create or overwrite an installation](/rest/api/notificationhubs/create-overwrite-installation) and set `platform` to `FCMV1`.
192192

0 commit comments

Comments
 (0)