One ticket versus two, and why it decides everything
The single fact that separates a protected connection from a gamble.
Azul draws a sharp line between a connection it sold you as one journey and a connection you assembled from separate flights. On a single Azul ticket, the connection is protected: if you miss the onward flight because Azul was late, Azul owes you a rebooking on the next available flight, and your bag is generally checked through to the final destination so you don't touch it in between. That protection is quiet but valuable, and it is the whole argument for keeping a trip on one ticket even when two separate ones look a little cheaper.
The moment the itinerary is two tickets, or a third-party booking that squeezed a tight layover, that protection is gone. Azul's contract (clause 9.1.1) explicitly disclaims liability for a missed connection on a self-built itinerary or a third-party booking with insufficient time. In plain terms: if you miss the next flight, that's your loss, you re-check your bag, you clear immigration yourself, and you buy a new ticket. A booking engine will happily sell you a 45-minute self-transfer as if it were seamless; it isn't, and this is precisely the trap we check for before you pay.
The Guarulhos terminal split, and the codeshare check-in rule
The section you cannot copy from a generic connections guide, because it is specific to Azul, GOL and GRU.
Azul has a domestic codeshare with GOL, which is genuinely useful, it widens where a single ticket can take you, but it hides a physical catch at São Paulo Guarulhos. Azul operates from Terminal 1 there and GOL from Terminal 2. So an Azul plus GOL connection at GRU is not a stroll to the next gate; it is a terminal change, with the walk, the signage and the minutes that involves. An itinerary will print that as one clean connection, and travellers plan for a gate change when the reality is a terminal change.
Treat an Azul-to-GOL or GOL-to-Azul connection at Guarulhos as a terminal transfer, not a quick hop. If the layover only makes sense as a same-terminal walk, it may not actually hold, so give it real time.
On a connecting codeshare, you check in with the airline that operates the first flight, which may not be the airline whose name you booked under. Confirm which counter is yours before you arrive, so you're not sent across the airport at the worst moment.
On a single codeshare ticket the bag is often through-checked; on separate tickets it isn't. Because the terminal change adds friction, knowing in advance whether you're carrying your bag between Terminal 1 and Terminal 2 changes how much time you actually need.
Terminal assignments and codeshare procedures are set by the airlines and airports and can change; confirm your terminals, check-in airline and bag handling for your specific itinerary before you travel.
Bags, immigration and the tight-layover math
What actually happens between two flights, and why a 50-minute gap can be a trap.
On one Azul ticket, the airline generally checks your bag through to the destination and moves it for you, so a connection is mostly about getting yourself to the next gate. On a self-built connection or separate tickets, the picture changes completely: you collect your checked bag at the belt, carry it, re-check it for the next flight, and clear any immigration or security the routing requires, all inside your layover. That is why a gap that looks generous on paper can be impossibly tight in practice, especially on an international connection or one that changes terminals.
The honest rule is to plan the connection around the worst-case version of it: bag in hand, a terminal to cross, and a queue you didn't expect. If the layover only works assuming everything goes perfectly, it doesn't really work. Tell us the routing and we'll tell you whether the bag is through-checked, whether immigration is in the middle, and how much time this specific connection genuinely needs, before you build a trip on a layover that was never long enough.
Before you book a connection, the checklist
Six answers now keep a layover from becoming a missed flight.
- Is it one Azul ticket? One ticket is protected; two tickets means a miss is your loss
- Is the layover generous? Azul publishes no minimum, so don't cut it fine, especially internationally
- Azul plus GOL at Guarulhos? Plan for a Terminal 1 to Terminal 2 change, not a gate walk
- Which airline do you check in with? On a codeshare, the operator of the first leg
- Is the bag through-checked? Confirm it, or budget time to collect and re-check
- Is there immigration in the middle? An international connection needs extra time for it
One ticket protects you; a tight self-connection doesn't. The two ways an Azul connection goes wrong are a self-built layover Azul never promised to protect, and the Guarulhos terminal change nobody budgeted for. Both are decided when you book, not at the airport. When you call us, we keep the journey on one protected ticket where we can, time the layover for the real-world version with the bag and the terminal change, and confirm the check-in airline, so the connection holds instead of collapsing.
Frequently asked
What is Azul's minimum connection time?+
Will Azul protect my connection if I misconnect?+
On an Azul and GOL codeshare, which terminal do I use at São Paulo Guarulhos?+
Does Azul handle my bags on a connection?+
Contact options
Reach Azul directly, or let us build the connection safely with you.
Contact Azul directly
The airline's own channels, free.
These are Azul's own channels. Confirm terminals, connection times and bag handling at voeazul.com.br and with your airports.
More Azul help
Related guides.